Skip to content

Latest commit

 

History

History
15 lines (12 loc) · 634 Bytes

RELEASE.md

File metadata and controls

15 lines (12 loc) · 634 Bytes
Raw

Recommended workflow

  1. Make changes
  2. Commit those changes
  3. Make sure Travis turns green
  4. Bump version in package.json
  5. Generate conventionalChangelog ( $ npm run changelog )
  6. Commit package.json and package-lock.md and CHANGELOG.md files
  7. Tag
  8. Push

The reason why you should commit and tag after conventionalChangelog is that the CHANGELOG should be included in the new release, hence gitRawCommitsOpts.from defaults to the latest semver tag.

Important: The npm run changelog command needs to be executed only from master branch.

More details at: https://www.npmjs.com/package/conventional-changelog-cli .