Open
Conversation
| ## Release Steps | ||
|
|
||
| 1. **Prepare the release:** Ensure all intended pull requests are merged and the main branch CI is passing. | ||
|
|
Contributor
There was a problem hiding this comment.
Here we also need a dedicated PR to update all the manifests so that they point to the new release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document the multi-arch release workflow: versioning policy, manual steps, automated CI/CD via GitHub Actions (binaries, container images on Docker Hub and GHCR, Helm chart, build provenance attestations), and security release process.