| Info | ||
|---|---|---|
| ||
For each module, update changelog to reflect changes since last release:
|
...
- raise a PR when necessary
- 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. If repository has been set up with github actions, then the NPM should already be being built from the tag.
(If github actions are NOT set up for the repository, the NPM has to be built manually, see below)
a. Check the actions tab in the repository on Github, and find the task for the NPM release
b. 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.
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. Select "Draft new release" from github on the right hand sid eof the repository page, and select your tag. Give it the name "Version x.y.z"
9. Paste the CHANGELOG for that module in the Describe this release section and click publish release
a. If this is a full release or patch release in bugfest, select "latest release", otherwise make sure that is not selected
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.
...