Allow labeled burndown version updates - #632
Open
msarahan wants to merge 4 commits into
Open
Conversation
msarahan
requested review from
KyleFromNVIDIA
and removed request for
a team
September 8, 2026 17:57
msarahan
added
non-breaking
msarahan
requested review from
gforsyth
and removed request for
KyleFromNVIDIA
September 8, 2026 19:34
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
1 participant
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.
Posted by Codex (GPT-5.6) on Michael Sarahan's behalf. Treat this message as LLM-generated.
During release burndown, the generated version-update PRs must change the repository VERSION file. The shared changed-file check currently rejects every such change, which leaves otherwise-valid burndown PRs unable to pass required CI.
This exempts PRs whose head branch uses the
version-update-YY.MMnaming convention produced by release-scripts. VERSION-file enforcement remains unchanged for PRs from other branches.The change targets
release/26.10because repositories in the active release need it now; the normal forward merge will then carry it tomainfor future burndowns.Validation: