...
Currently, we have 9 UI modules within ERM:
stripes-erm-components
- ui-agreementsui-licenseshandler-stripes-registry
- ui-dashboarduiplugin-ermfind-comparisonsagreement
- ui-localplugin-kbfind-admineresource
- ui-plugin-find-agreementlicense
- ui-plugin-find-licensedashboard
ui-agreements
ui-licenses
ui-plugin-find-eresource-local-kb-admin
- ui-erm-comparisons
We follow the FOLIO version-numbering scheme to version our apps/plugins. This is the same as the official semver documentation.
...
Important note: Its mandatory that the stripes-erm-components needs to be the first module that has to be released. This is because all the other UI modules have a dependency on it and the build will fail for them if they can't find the expected stripes-erm-components version from the https://repository.folio.org/#browse/browse:npm-folio repository.
This logic also holds for the module ui-handler-stripes-registry and any plugins used directly by our applications.
Suggested order is as listed above.
Assuming, we are releasing version 3.0.0 for a UI module and that you are on the up to date master branch for that module (at this point you have the CHANGELOG and probably package.json that are still uncommited):
...