Info | ||
---|---|---|
| ||
For each module, update changelog to reflect changes since last release:
|
...
5) Once steps 1-3 are done, edit the CHANGELOG . Example PR
- Check release ticket (e.g. ERM-3101) for corresponding linked issues since last release date
Check filter page for each component,
to find all related Issues, edit this JIRAsearch:No Format project = erm AND resolution is not EMPTY AND resolution != "Cannot Reproduce" AND resolution != "Won't Do" AND resolutiondate >= 2023-10-
...
21 AND component = stripes-erm-components ORDER BY created ASC
update resolutionDate to last release date +1:
Info If you filter by last release date you will find the last release Jira ticket and occassionally last tickets before release. So you should filter by last release day +1
You find the release date on github repository's sidebar under the Releases section as Latest tag.
Example:
Link example:
https://github.com/folio-org/stripes-erm-components/releases/tag/v9.0.1- update component
- Check commit history since last release (from example)
- OPTIONAL (if not done here, do it later at end of release process):
update the release date from In progress to the date of release
At this point the modules are ready to be released
(OPTIONAL: set the related Jira ticket from DRAFT to OPEN to indicate they are ready for any dependency changes and release completion)
Release process:
Important note: Its mandatory that the stripes-erm-testing needs to be the first module that has to be released if any changes have occurred. This is because all the other UI modules have a dev dependency on it and so the release task running the tests will fail for them if they can't find the expected stripes-erm-testing version from the https://repository.folio.org/#browse/browse:npm-folio repository.
...