Skip to content

Latest commit

 

History

History
13 lines (8 loc) · 961 Bytes

RELEASING.md

File metadata and controls

13 lines (8 loc) · 961 Bytes

Releasing a new version

We are using GitHub Actions to create the release pages, binary artifacts, and Docker images for a given release. In the actions we also use the tool Knope to do semantic versioning.

Knope will follow conventional commits so if you annotate your PR titles with the appropiate prefix, that will pick up to do a minor or patch version. If you need to manual increment the version you can make an empty commit following the conventional commit pattern.

Running the action

  • Navigate to the Build and Release action
  • Trigger a new workflow and pass in the new version you expect to release given all the previous commit history
    • The string is the semver string minus the v prefix so if you pass in 1.2.3 the release will be cut as v1.2.3