| Info | ||
|---|---|---|
| ||
For each module, update changelog to reflect changes since last release:
|
...
2) Run yarn test across all the modules and make sure there are no test failures. (Note: No tests for the plugins and registry-handler)
3) Manually browse through individual modules with the browser console open and ensure there are no glaring warnings/errors in the console.
...
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.
...