Publishing Releases

The core artifact for this project is the RPM, as such the GitHub release process is built into the Release RPM actions workflow.

About the RPM workflow

The workflow executes on every PR and push to master to guarantee that the RPM build process has not been disturbed.

todo;; add note on integration testing the RPM installation

Releasing is a semi-automated process

The release workflow is semi-automated. The release action will generate a draft release containing the RPM artifacts, but a maintainer is required to review and publish the draft manually. This removes the burden of crafting releases, but still provides the safety of a final sign-off of the materials in the release.

When are draft releases created?

When a tag is pushed that matches a predefined regex pattern the workflow will add a stage to publish the draft release. Another regex will be checked to determine if the release should be flagged as a "prerelease".

regex patterns

In the workflow github.ref is checked against these patterns:

Condition	Regex	Position
create release	refs/tags/v*	starts with
is prerelease	refs/tags/v0	starts with
is prerelease	rc	contains