Skip to content

docs: recommend the @v0 moving major tag + Versioning section#168

Merged
reuvenharrison merged 1 commit into
mainfrom
docs/recommend-v0-tag
Jun 16, 2026
Merged

docs: recommend the @v0 moving major tag + Versioning section#168
reuvenharrison merged 1 commit into
mainfrom
docs/recommend-v0-tag

Conversation

@reuvenharrison

Copy link
Copy Markdown
Contributor

Publishes and documents a moving major-version tag.

  • The v0 tag is now published (pointing at the latest stable release) and is re-pointed on every stable release by the release tooling, so @v0 users get later patches and minors (e.g. the review/PR-comment improvements) automatically, with no workflow change.
  • README examples switch from the exact @v0.1.1 pin to @v0.
  • New Versioning section explains @v0 (recommended), exact pins (@v0.1.1, for reproducible CI), and @main (unreleased tip).

Motivation: the action only published exact patch tags, so a tag-pinned user never got a fix without manually re-pinning. @v0 closes that gap (like the common @v1 pattern). @main users already track the tip; @v0 gives the same auto-update with release gating.

🤖 Generated with Claude Code

Pin examples at @v0 (the moving major tag, now published) so users get later
patches and minors automatically, including the review and PR-comment
improvements. Add a Versioning section explaining @v0 (recommended), exact
pins (@v0.1.1) for reproducible CI, and @main for the unreleased tip.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@reuvenharrison reuvenharrison merged commit e245290 into main Jun 16, 2026
56 checks passed
@reuvenharrison reuvenharrison deleted the docs/recommend-v0-tag branch June 16, 2026 13:29
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