-
Notifications
You must be signed in to change notification settings - Fork 2
Release Process
Matt Yoder edited this page Sep 4, 2025
·
2 revisions
Please follow these steps to make a new release of @access-ci/ui
:
-
Use conventional commits in the working branch, or in the merge commit when merging a pull request. To trigger a new release, the CI workflows need to see commits of type
feat
orfix
. -
Once
feat
orfix
commits have been merged into themain
branch, a release pull request will be created. Review and merge the pull request to make a new release on GitHub and publish it to NPM.
To create a beta release, push an empty commit with the name of the version:
git commit --allow-empty -m "chore: release 0.10.0-beta1" -m "Release-As: 0.10.0-beta1"
git push