Page Comparison

...

1. raise a PR when necessary
2. set the related Jira ticket from DRAFT to OPEN to indicate they are ready for any dependency changes and release completion

At this point the modules are ready to be released

...

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 modulesee below)
    7b.2a. Login to jenkins and check for the 3.0.0 tag fromCheck the actions tab in the listrepository (fromon theGithub, dropdownand besidefind the tag,task clickfor the build now button) NPM release
    7bb.3. Once the buildaction has startedpassed, you can click the full stage view option to see the build
    7b.4. Wait for the build to be all done and green, then navigate to https://repository.folio.org/#browse/browse:npm-folio and see if your module has been published.
8. 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.
9. Paste the CHANGELOG for that module in the Describe this release section and click publish release
10. 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.

...

For further information on the patch/hotfix release procedure refer to this section https://github.com/folio-org/stripes/blob/master/doc/release-procedure.md#patch-release-procedures from the official stripes release documentation.

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)
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)
7b.3. Once the build has started you can click the full stage view option to see the build
7b.4. Wait for the build to be all done and green, then navigate to https://repository.folio.org/#browse/browse:npm-folio and see if your module has been published.

FAQs:

todo