Repository navigation
Automate release candidates and publication from release branches - #125
Merged
Merged
Conversation
svvarom
reviewed
Nov 2, 2026
nicot
approved these changes
Nov 3, 2026
callingmedic911
enabled auto-merge (squash)
November 5, 2026 21:05
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
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.
Keep development on
mainwhile QA tests a separate release branch. Replace Prepare release with Start release and Publish release.For example, releasing
0.3.0:release/0.3.0and draft pre-releasev0.3.0rc1with QA artifacts.rc2and opens a forward-port PR to main. CI starts automatically using the service-account token; the PR auto-merges once checks and approvals permit.v0.3.0rc2rebuilds and validates the final package, stages its wheel in NGC, and publishes the final GitHub release.Publication stops if the release branch has moved beyond the selected candidate. Only final releases go to NGC. PyPI publishing stays separate.