Repository navigation
[release]: Cut patches from per-minor release branches - #237
Merged
Merged
Conversation
Starting with v1.0 we support the current minor and the two before it, so critical fixes need to ship on older lines. Releases could only be cut from main, and every release took latest on GitHub and Docker Hub, so a patch to an older line would have taken latest from a newer one. Each minor now gets a _releases/vX.Y.x_ branch, which the workflow creates when it releases vX.Y.0 from main. main cuts minor and major releases, release branches cut patches for their line only. `svu` picks the highest tag in the whole repo regardless of branch, so on a release branch it is limited to that line's tags with `--tag.pattern`. A release is marked latest only when it is the highest stable version. The workflow passes that to goreleaser as MAKE_LATEST, which controls both make_latest and the latest image tag. This also stops prereleases from taking the latest image tag. CI now runs for release branches so backport PRs are checked, and CONTRIBUTING covers the support window and how to backport, including fixes that need adapting rather than a clean cherry-pick.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
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.
Starting with v1.0 we support the current minor and the two before it, so critical fixes need to ship on older lines. Releases could only be cut from main, and every release took latest on GitHub and Docker Hub, so a patch to an older line would have taken latest from a newer one.
Each minor now gets a releases/vX.Y.x branch, which the workflow creates when it releases vX.Y.0 from main. main cuts minor and major releases, release branches cut patches for their line only.
svupicks the highest tag in the whole repo regardless of branch, so on a release branch it is limited to that line's tags with--tag.pattern.A release is marked latest only when it is the highest stable version. The workflow passes that to goreleaser as MAKE_LATEST, which controls both make_latest and the latest image tag. This also stops prereleases from taking the latest image tag.
CI now runs for release branches so backport PRs are checked, and CONTRIBUTING covers the support window and how to backport, including fixes that need adapting rather than a clean cherry-pick.