Skip to content

Add tag refs to nbgv publicReleaseRefSpec#511

Open
corinagum wants to merge 1 commit into
mainfrom
cg/nbgv-tag-public-release
Open

Add tag refs to nbgv publicReleaseRefSpec#511
corinagum wants to merge 1 commit into
mainfrom
cg/nbgv-tag-public-release

Conversation

@corinagum
Copy link
Copy Markdown
Collaborator

Summary

  • CD pipeline triggered from a v* tag was producing 2.0.7.1 instead of 2.0.7 because Nerdbank.GitVersioning did not treat tag refs as public releases
  • Adds ^refs/tags/v\d+(?:\.\d+(?:\.\d+)?)?$ to publicReleaseRefSpec in version.json so builds from tags like v2.0.7 get a clean three-part NuGet version

Test plan

  • Trigger CD publish pipeline from a v* tag and confirm the produced NuGet package version is 2.0.x (no trailing .1)

🤖 Generated with Claude Code

…uce clean versions

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings May 15, 2026 00:32
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a tag ref pattern to nbgv's publicReleaseRefSpec so CD builds triggered from v* tags produce clean three-part NuGet versions instead of appending a height suffix.

Changes:

  • Append ^refs/tags/v\d+(?:\.\d+(?:\.\d+)?)?$ to publicReleaseRefSpec in version.json.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@corinagum
Copy link
Copy Markdown
Collaborator Author

False alarm - ADO confused me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants