Skip to content
This repository was archived by the owner on Feb 18, 2026. It is now read-only.

Release procedure

Jump to bottom
Ekaterina Sosinovich edited this page Oct 10, 2022 · 1 revision

Patch release

Version autoupdate is set up using the Github Actions. After the feature branch is merged into master branch, the patch version is incremented automatically by version-auto-increment workflow. After that new verapdf_gui docker image with the latest tag will be released by docker-images workflow.

Minor and Major releases

Minor and major version updates should be performed manually. Follow the steps, assuming X.X.X is the version to be released:

  1. Update version and release date

    1.1. Update "version" in package.json file to "X.X.X".

    1.2. Update REACT_APP_VERSION_DATE variable value in .env file to date of release in format Month D, Yr (e.g. October 10, 2022).

    1.3. Update version and date in /landing/assets/version.txt to X.X.X - Month D, Yr (e.g. 0.1.0 - October 10, 2022).

  2. Commit changes from step 1 with the commit message vX.X.X.

  3. Add tag with name X.X.X to the commit created at step 2 and push tag to remote:

     git tag X.X.X
 git push origin X.X.X

After these steps new verapdf_gui docker image with the X.X.X tag will be released by docker-images-tagged workflow.

Clone this wiki locally