Skip to content

Latest commit

 

History

History
24 lines (18 loc) · 1.16 KB

RELEASE.md

File metadata and controls

24 lines (18 loc) · 1.16 KB

Release

Versioning should follow Semantic Versioning

The build steps to releasing a new version. Before you can do this you need to to make sure the node packages are up to date - npm update

  • Make sure all tests pass - karma start or grunt test
  • Commit and push all changes with a meaningful message
  • Update version in bower.json and package.json
  • Build the dist folder - grunt build
  • Commit and push with the message "Bumping to v*.*.*"
  • Create a new release
    • Tag version is v*.*.*
    • Release title is "Angular Dynamic Form v*.*.*"
    • The comment section should be a list of commits and the changes the commit made. See below for an example
    • If it is under v1.0.0 then mark "This is a pre-release" as true

Example github release comment

Changelog:

  • 33efce58357b654bc3ec7c5d59e5b36503d5bb13 - [BUGFIX] Fixing spaces in automatic api endpoint
  • ba36c1d5e3a30c6de295771adb59a51ce151c25b - [BUGFIX] Fixing #1: Improve bower.json ignore
  • 93e89af673509d075dfc8c6137d97645ab392646 - Bumping to v0.1.2