Fix release workflow to strip 'v' prefix from version tag - #3
Merged
Merged
Conversation
NuGet version strings don't support the 'v' prefix. The workflow extracts the git tag (e.g., v1.0.0-beta.13) and strips the 'v' to get the proper NuGet version format (1.0.0-beta.13). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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.
Summary
Problem
The release workflow was extracting the full git tag name (e.g.,
v1.0.0-beta.13) and passing it directly to the/p:Version=parameter. NuGet version strings don't support the 'v' prefix, causing build errors:Solution
Added a simple bash parameter expansion to strip the leading 'v':
This transforms
v1.0.0-beta.13→1.0.0-beta.13which is valid for NuGet.Test plan
🤖 Generated with Claude Code