...
1. git checkout -b 'v3.0'
2. git add package.json CHANGELOG.md
3. git commit -m 'Release 3.0.0'
4. git tag v3.0.0
5. git push --set-upstream origin v3.0
6. git push --tags
7.
7a. If repository has been set up with github actions, then the NPM should already be being built from the tag.
7a.1. Check the actions tab in the repository on Github, and find the task for the NPM release
7a.2. Once the action has passed, you can navigate to https://repository.folio.org/#browse/browse:npm-folio and see if your module has been published.
7b. If github actions are NOT set up for the repository, the NPM has to be built manually.
7b.1. Navigate to https://jenkins-aws.indexdata.com/job/folio-org/job/ui-agreements/view/tags/ (assuming you are releasing the ui-agreements module)
8 7b.2. Login to jenkins and check for the 3.0.0 tag from the list (from the dropdown beside the tag, click the build now button)
9 7b.3. Once the build has started you can click the full stage view option to see the build
10 7b.4. OnceWait for the build to isbe all done and green, youthen can navigate to https://repository.folio.org/#browse/browse:npm-folio and see if your module has been published.
118. Navigate to https://github.com/folio-org/ui-agreements/tags and you should see the tag there. Click on it and draft a new release.
129. Paste the CHANGELOG for that module in the Describe this release section and click publish release
1310. Send the release announcement to the #releases slack channel once done.
After the release:
1) Merge the branches pushed to github for the respectve modules into their masters
2) Bump the minor versions of all the UI modules with a new CHANGELOG version entry so that any new code being added doesn't accidentally go towards the just released version.
...