Skip to content

Fix GitVersion tag-prefix for package-name@version tag format #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shellicar merged 2 commits into from
Apr 13, 2026
Merged

Fix GitVersion tag-prefix for package-name@version tag format #21

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7fa27ca
Fix GitVersion tag-prefix for package-name@version tags
shellicar Apr 13, 2026
0a5d9a5
Rewrite testament, remove ConfiguredNextVersion strategy
shellicar Apr 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions .claude/testament/2026-04-13.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,7 @@
# 23:17
# GitVersion tag-prefix for package-name@version tags

This was a straightforward docs PR. Nothing technical to solve.
## The trap: next-version conflicts with tag-prefix regex

The prompt ran twice because the first worker's version didn't include the "do not commit" instruction (it was added silently after dispatch). The PM post-mortem is documented in the prompt itself.
GitVersion applies `tag-prefix` when parsing `next-version` too, not just when matching git tags. Setting `tag-prefix: '.*@'` while `next-version: 1.0.0` is present causes a crash: "Failed to parse 1.0.0 into a Semantic Version" because `1.0.0` has no `@` to match.

The second Phase 1 run found a merge conflict in `.claude/CLAUDE.md` on main that the Supreme Commander had already resolved. The staged resolution carried over to the feature branch cleanly when it was created from origin/main.

No CI surprises expected. The only files changed are `README.md`, `.claude/CLAUDE.md`, and this testament.
The fix is to remove `next-version` entirely. `next-version` is only meaningful for workflows that don't use tags to track releases. This workflow does. It was never needed.
3 changes: 1 addition & 2 deletions GitVersion.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,6 @@
next-version: 1.0.0
increment: Patch
tag-prefix: '.*@'
strategies:
- ConfiguredNextVersion
- MergeMessage
- TrackReleaseBranches
- VersionInBranchName
Expand Down
Loading