Repository navigation
Use GitVersion and let GA and rc tags publish to nuget.org - #728
Merged
dennisdoomen merged 1 commit intoOct 22, 2026
Conversation
dennisdoomen
added
enhancement
- Replace Nerdbank.GitVersioning and version.json with GitVersion (GitFlow preset). develop builds are -alpha.N, release/* builds are -beta.N. - Tags have no "v" prefix. The release workflow passes the tag to the build as ReleaseTag, and the tag becomes the package version. - GA and -rc tags publish to nuget.org without approval. Other prerelease tags skip nuget.org. - Preview workflow also runs on release/** pushes. - Prune workflow also removes old -alpha and -beta versions. - Add ADR-0011 and update the release docs. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
dennisdoomen
force-pushed
the
feature/gitversion-tag-driven-releases
branch
from
October 22, 2026 19:53
38df22b to
fc01d7b
Compare
dennisdoomen
marked this pull request as ready for review
October 22, 2026 20:08
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
v10.5.0-rc.2built as10.5.0-preview.31. The version came fromversion.json, and nobody changed it on the release branch. The tag did not set the version.nuget.org also needed a manual dispatch and an approval for every release.
Outcome
Versions come from the branch and the tag. A tag push is enough to release. See ADR-0011.
develop-alpha.Nrelease/*-beta.NX.Y.Z-rc.NorX.Y.ZChanges
GitVersion.yml, GitFlow preset) replaces Nerdbank.GitVersioning.version.jsonis deleted.vprefix. The release workflow passes the tag to the build asReleaseTag, and the tag is the package version.nuget-orgenvironment in repo settings.refs/tags/[0-9]*to tag ruleset 17017817. It only coversrefs/tags/v*now, so without this any writer can push10.5.0and publish to nuget.org.release/**. The prune workflow also removes old-alphaand-betaversions.cutting-a-releaseskill updated.Checked
dotnet-gitversiongives10.5.0-beta.1onrelease/v10.5andrelease/10.5,10.5.0-alpha.Nondevelop,10.4.1-Nonmainand10.3.24-Nonsupport/v10../build.ps1 Packworks locally.Compile --release-tag 10.5.0-rc.3works, and--release-tag v10.5.0fails with a clear message.-rctag after merge is the real test.Notes
Major.Minor.0.0(assembly-versioning-scheme: MajorMinor), the same for branch and tag builds.v10.5.0-rc.2tag and its empty immutable release stay. Use10.5.0-rc.3next.🤖 Generated with Claude Code