Release process

Maintainers have the ability to run the Stage Release workflow. Running this workflow will:

After the draft release has been created, edit it and populate the description. Once you are done, click “Publish release”.

After the release is published, the Promote Release workflow will run automatically. This workflow will:

  • Publish receptorctl to PyPI.
  • Pull the container image from ghcr.io, re-tag, and push to Quay.io.
  • Build binaries for various OSes/platforms, and attach them to the release.

Note

To customize packaging and allow for tags that do not strictly satisfy the semantic versioning given to development releases, the current workflow uses simple make to build and archive binaries, instead of specific tools for build and release.