Restore stable 9.4 versioning on release/9.x#1123
Merged
JakenVeina merged 1 commit intoJun 30, 2026
Merged
Conversation
JakenVeina
approved these changes
Jun 30, 2026
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.
Problem
release/9.xcannot publish. PR #1088 overwrote this branch''sversion.jsonwith main''s preview line, so HEAD declares"version": "9.5-preview.{height}". NBGV computes9.5.0-preview.2, and the policy step inrelease.ymlrefuses to publish a prerelease from arelease/*.xbranch, so the branch is stuck.Fix
Restore the stable form. This branch ships stable
9.4.x, and the latest published version (the tag on this repo and the package on NuGet.org) is9.4.31:The base-version flip
9.4 -> 9.5 -> 9.4resets NBGV''s git height to 1 on the commit that re-introduces9.4, so the offset is required to keep the patch number continuous.Verification
nbgv get-version, evaluated on the post-merge topology (one commit on the current HEAD, on arelease/9.xref):Next publish is a clean stable
9.4.32, continuing from9.4.31. Offset 31 is the minimum safe value; 30 would compute9.4.31and collide with the existing release.Label
Labeled
manual-version-editsopr-version-check.ymlpermits the hand edit. This is the recovery case the label is documented for.