Skip to content

docs: add tag format warning to release command#23

Merged
anilcancakir merged 1 commit intomainfrom
chore/release-command-tag-warning
Apr 6, 2026
Merged

docs: add tag format warning to release command#23
anilcancakir merged 1 commit intomainfrom
chore/release-command-tag-warning

Conversation

@anilcancakir
Copy link
Copy Markdown
Contributor

Summary

  • Added critical warning to .claude/commands/release.md about tag format: NO v prefix
  • publish.yml triggers on [0-9]+.[0-9]+.[0-9]+* — a v-prefixed tag silently skips the pipeline

Context

During 0.0.1-alpha.10 release, the tag was initially created as v0.0.1-alpha.10 which didn't trigger publish. Had to delete and recreate as 0.0.1-alpha.10.

The publish.yml workflow triggers on tags matching [0-9]+.[0-9]+.[0-9]+*
(no v prefix). Added explicit warning to prevent using v-prefixed tags
that silently skip the publish pipeline.
Copilot AI review requested due to automatic review settings April 6, 2026 23:55
Copy link
Copy Markdown

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

Updates the internal release command documentation to prevent CI/CD publish failures caused by creating v-prefixed git tags, which do not match the tag trigger pattern used by the publish.yml workflow.

Changes:

  • Added a prominent warning that release tags must be {version} with no leading v.
  • Documented the exact tag pattern that triggers the publish.yml workflow.

Comment thread .claude/commands/release.md
@sentry
Copy link
Copy Markdown

sentry bot commented Apr 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@anilcancakir anilcancakir merged commit 63bf945 into main Apr 6, 2026
6 checks passed
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.

2 participants