chore(release): Bump version.json to 2.1#297
Merged
Merged
Conversation
The 2.1.0 stable packages were published from the v2.1.0 tag (which forces the version via nbgv set-version + /p:Version). Bump the declared base version so non-tag CI dev builds compute 2.1.x instead of 2.0.x. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Aligns the repository’s Nerdbank.GitVersioning base version with the already-published 2.1.0 release line so that non-tag CI/dev builds compute 2.1.x rather than 2.0.x.
Changes:
- Bump
version.json"version"from2.0to2.1to match the 2.1 release line.
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.
What
Bumps the declared base version in
version.jsonfrom2.0to2.1.Why
The 2.1.0 stable NuGet packages were published from the
v2.1.0tag, where the Release workflow forces the version (nbgv set-version+/p:Version=2.1.0). Butversion.jsonstill declared2.0, so non-tag CI dev builds compute2.0.x(Nerdbank.GitVersioningSimpleVersion). This bump aligns dev builds with the released line so they compute2.1.x.This does not affect any published package — released versions are determined by the tag, not
version.json.Testing
version.jsononly. CI builds will confirm versioning resolves to2.1.xon this branch.