The release schedule for this project is ad-hoc. Given the pre-1.0 status of the project we do not have a fixed release cadence. However if a vulnerability is discovered we will respond in accordance with our security policy and this response may include a release.
There is a semi-automated release process for this project. When you create a Git tag with a tagname that has a v
prefix and push it to GitHub it will trigger the release workflow.
The release process for this repo is documented below:
- Create a tag for the new release:
export VERSION=v0.6.0-alpha.0 git tag --annotate --message="Release ${VERSION}" "${VERSION}" git push origin "${VERSION}"
- A GitHub action will see the new tag and do the following:
- Build and publish any container images
- Build and publish the Helm chart
- Create a draft GitHub release
- Upload the Helm chart tarball to the GitHub release
- Visit the releases page, edit the draft release, click "Generate release notes", then edit the notes to add the following to the top
openshift-routes provides OpenShift Route support for cert-manager
- Publish the release.
This repo will produce the following artifacts each release. For documentation on how those artifacts are produced see the "Process" section.
- Container Image - Container image for openshift-routes is published to
ghcr.io/cert-manager/cert-manager-openshift-routes:vX.Y.Z
. - Helm chart - An official Helm chart is maintained within this repo and published to
ghcr.io/cert-manager/charts/openshift-routes:X.Y.Z
.