Page Comparison

...

Its also important to understand the different types of dependencies that exist within the package.json. This is a good documentation that explains the different types of dependencies and their purposes.

Before you release (Pre-release process):

By this time, it is considered that all your UI modules are synchronized with the relased stripes version and you have also updated your UI modules to their respective major/minor version.

...

3) Manually browse through individual modules with the browser console open and ensure there are no glaring warnings/errors in the console.

4) OPTIONAL (can be done during the actual release process):
Go through all the dependencies in the package.json and verify if all of the ones that require updation are updated (Note: Each of the erm UI modules depends on stripes-erm-components, so its important that each of those modules is dependent on  the version of stripes-erm-components that is going to be released)

5) Once the above steps 1-3 steps are done, edit the CHANGELOG . Example PR

1. Check release ticket (e.g. ERM-3101) for corresponding linked issues since last release date

2. 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-20 AND component = stripes-erm-components ORDER BY created ASC

   
   

   1. update resolutionDate to last release date:

      Info
      You find the release date on github repository's sidebar under the Releases section as Latest tag. Example: Image Added Link example: https://github.com/folio-org/stripes-erm-components/releases/tag/v9.0.1

      
      

   2. update component
3. Check commit history since last release (from example)
4. 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.

...