The release management process of Open-BPMN is based on the Releasemanagement and versioning of the Imixs Workflow main project. Because the project contains a Java part and JavaScript (Node.JS) part also the release process is split into two parts. The java part is based on the Maven Release Plugin, the JavaScript part is based on nmp.
A release can be performed by calling the script "release.sh". This script is as far as possible automated. It releases the current maven snapshots and publish the node.js modules into the Open-BPMN nmp repository.
Before you start the release process verify if the general build of open-bpmn is successful:
$ mvn clean install
$ ./scripts/build.sh -i
Check current release status on npm:
https://www.npmjs.com/settings/open-bpmn/packages
To be able to publish to the npm repository (https://www.npmjs.com/) you need to login during the release process with your npmjs.com account. Alternatively you can create an automation token and set this token in your local environment first!
$ cd open-bpmn.glsp-client/
$ npm config set _authToken=%YOUR_ACCES_TOKEN%
Replace %YOUR_ACCES_TOKEN% with a valid Token!
Now you can run the release script:
$ ./scripts/release.sh
Finally commit your changes.
If you not run the release script you can also bumping the version number of OpenBPMN using a script:
$ changeVersion.sh <oldVersionString> <newVersionString>
Specify the old and the new version. Example:
$ changeVersion.sh 0.3.0 0.4.0
Finally commit your changes.