Skip to content

Releasing

The release process is pipeline-driven. Never bump the version, write a Release vX.Y.Z commit, or create a tag by hand — these are owned by the release pipeline. There is no changelog.

Release Process

  1. A developer manually runs the bump_version job in the GitLab CI pipeline at https://gitlab.racom.eu/dev/mirror/rades_react/-/pipelines/new:

    1. Populate the bump_version parameter by selecting the type of version bump (major, minor, or patch).
    2. Click the New pipeline button.

  2. The bump_version job:

    • Updates the version number in package.json and package-lock.json on the master branch.
    • Commits the change to a new branch and pushes it to the remote.
    • Creates and merges that branch into master via a Bitbucket pull request.
    • Tags the commit (now on master) and pushes the tag.

  3. A tagged commit triggers the CI/CD pipeline that:

    • Publishes the package to the npm registry.
    • Deploys the documentation.
    • Opens pull requests in Bitbucket to update the RADES version in the consumer applications RA2W (ra2_ui_web_client) and WECL (web_client).

Reference