Skip to content

ci: a final release tag is not a prerelease - #49

Merged
zeyuyang42 merged 1 commit into
mainfrom
ci-prerelease-suffix
Oct 16, 2026
Merged

zeyuyang42 merged 1 commit into
mainfrom
ci-prerelease-suffix

Conversation

@zeyuyang42

Copy link
Copy Markdown
Collaborator

Summary

The release job decided --prerelease with case "$GITHUB_REF_NAME" in *-*). Every host tag contains a hyphen in its prefix (max-v, pd-v), so the final max-v0.3.0 draft came out as a prerelease. The check now looks at the version part only, so max-v0.3.0-rc1 stays a prerelease and max-v0.3.0 does not.

The max-v0.3.0 draft itself was corrected with gh release edit --prerelease=false; this PR fixes the next one.

Test plan

  • Logic read through: VERSION is ${tag#max-v} from the guard step, so 0.3.0 has no hyphen and 0.3.0-rc1 does
  • Next release tag (either host) comes out prerelease=false

🤖 Generated with Claude Code

The release job marked every release as a prerelease because it looked for a hyphen in the
whole tag name, and max-v0.3.0 has one in its host prefix. Test the version part instead, so
only a suffixed version (0.3.0-rc1) becomes a prerelease. Seen on the max-v0.3.0 draft, which
was corrected by hand with gh release edit.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@zeyuyang42
zeyuyang42 merged commit adf757d into main Oct 16, 2026
8 checks passed
@zeyuyang42
zeyuyang42 deleted the ci-prerelease-suffix branch October 16, 2026 23:57
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