Skip to content

Fix release tag patterns in CI - #397

Merged
mauroservienti merged 2 commits into
masterfrom
fix-release-tag-regex
Oct 6, 2026
Merged

mauroservienti merged 2 commits into
masterfrom
fix-release-tag-regex

Conversation

@mauroservienti

@mauroservienti mauroservienti commented Oct 6, 2026 •

Copy link
Copy Markdown
Owner

The release job classifies tags with [0-9]+.[0-9]+.[0-9]+$, which is not anchored at the start and uses unescaped . (matches any character). Any pre-release tag ending in three numeric segments is classified as production and pushed to NuGet.org, e.g.:

Tag Before After
3.0.0 production production
3.0.0-beta.9 pre-release pre-release
3.0.0-beta.7.1 pre-release pre-release
3.0.0-rc.1.2.3 production pre-release

Existing tags were all classified correctly; this closes the latent gap. The pattern is now ^[0-9]+\.[0-9]+\.[0-9]+$, and github.ref_name is quoted.

Tag triggers also only allowed a single-digit major and patch: [0-9].[0-9]+.[0-9] did not match 3.0.10 or 10.0.0, so no workflow ran and nothing was published. Now [0-9]+.[0-9]+.[0-9]+ and [0-9]+.[0-9]+.[0-9]+-*.

🤖 Generated with Claude Code

https://claude.ai/code/session_01AixzAbo1zbJgxpHo7vyoSc

mauroservienti and others added 2 commits October 6, 2026 09:51
@mauroservienti mauroservienti changed the title Anchor release tag regex in CI Fix release tag patterns in CI Oct 6, 2026
@mauroservienti
mauroservienti merged commit 937a1d3 into master Oct 6, 2026
3 checks passed
@mauroservienti
mauroservienti deleted the fix-release-tag-regex branch October 6, 2026 08:09
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.

1 participant