Warning
This package is deprecated. The content is moved to the @teamleader/ahoy package. The further development of the project will be closed-source but the package will be published under the new name.
-
Pull the
next-releasebranch to make sure you have all the latest code on your local machine. -
Make a new branch, starting from
next-releaseand give it the name of the next version you want to release (release/new.version.number). -
Bump the version in
package.jsonand commit with messageVersion bumpand push. -
Update
CHANGELOG.md-
Replace
[unreleased]with the[new.version.number]and add the releasedate next to it, like this- yyyy-mm-dd`. -
Clean up the unused titles.
-
Prepare for next release by adding the following content on top of the file:
## [unreleased] ### Added ### Changed ### Deprecated ### Removed ### Fixed -
Commit with message
Update changelogand push.
-
-
Make a
pull requeston Github where you add thechangelog itemsas the description and wait for approval. -
Make a
draft releaseon Github and fill in the following fields:- Tag version:
new.version.number@target: next-release - Release title:
new.version.number - Description: add the
changelog items
- Tag version:
-
Once the pull request has the needed amount of approvals, merge it into the
next-releasebranch. -
Publishthe earlier createddraft releaseon Github. -
In your
console, pull thenext-releasebranch. -
Publishtonpmusing thenpm publish --access=publiccommand. -
Mergethenext-releasebranch intomasterand push to Github