-
Ensure updates are listed in CHANGLOG.md in the
[Unreleased]
section. Once you trigger a new release, unreleased changes are automatically moved under the new version heading. -
Navigate to Actions and run the Release package workflow.
or, trigger the Release from the command line
brew install gh gh auth login gh workflow run "Release package" -f release-type=minor
Note: Valid release types are:
- patch, minor, major, prepatch, preminor, premajor, and prerelease
Pre-releases are tagged with '-beta.N', where N is incremented.
or...
-
Update CHANGELOG.md by moving any changes in the
[Unreleased]
section to a new release section## Unreleased ## 0.1.0 - 2024-07-02 ### Added - Initial Version
And commit it with
git add CHANGELOG.md && git commit -m 'chore: Update CHANGELOG.md
-
Ensure all unit tests pass with
npm test
-
Use
npm version major|minor|patch
to increment the version in package.json and tag the release -
Push the tags
git push origin master --tags
-
Publish the release
npm publish ./