-
Notifications
You must be signed in to change notification settings - Fork 1
Publishing
We use release-it to generate releases. Release-it should only be run on the main branch, after the features are merged.
The configuration is set, all you should need to do is run the following:
yarn releaseThis will prompt you for the following to complete the release:
-
Select increment (next version)- Major for breaking changes, minor for feature additions, patch for fixes/ chores -
Publish ember-validation-state to npm?- This will publish a new package to the npm package registry (y) -
Commit (chore: release x)?- This will create a new commit to be tagged on the main branch (y) -
Tag (x)?- Create tag for the release (y) -
Push?- Push tags and commit to master (y) -
Create a release on GitHub (Release 0.1.0)?- Creates release in Github UI (y)
This will also add updates to the CHANGELOG.md, which will go along with the release commit.