fix: honest versioning — @v0 moving alias, SHA-first, auto-advance on release (#22) - #23
Merged
Merged
Conversation
Root cause: no release automation, so the moving @v1 tag was never advanced (it pointed at v0.1.1, 3 releases behind v0.1.4). @v1 is also semantically wrong for a 0.x project (there is no v1.x). - README Versioning: SHA-first (what saw guard setup emits) -> exact @v0.1.4 -> moving @v0/@v1 (advanced at release time; prefer a SHA). @v1 documented as a deprecated legacy alias. - examples/worm-guard.yml: pin @v1 -> @v0.1.4 (a real release tag). The one-time tag catch-up (@v0 created, @v1 moved to v0.1.4) is done directly on the tags, not in this PR. NO CI automation force-moves tags: a privileged auto-promotion of consumer-trusted aliases would expand attack surface and skip review (contrary to our reviewed-bump doctrine) — deliberately avoided. Relates to Ndevu12/stayAwakeBot#1229.
Ndevu12
force-pushed
the
fix/versioning-tag-hygiene-22
branch
from
July 18, 2026 21:17
1f293c5 to
e3fa676
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the stale
@v1tag + misleading versioning guidance (#22).Root cause: the moving
@v1tag was never advanced — it still pointed at v0.1.1 (3 releases behind v0.1.4). And@v1is semantically wrong for a0.xproject (there is no v1.x).This PR (docs only)
saw guard setupemits) → exact tag@v0.1.4→ the moving@v0/@v1aliases (advanced at release time; a SHA is preferred).@v1documented as a deprecated legacy alias.examples/worm-guard.yml— pin@v1→@v0.1.4(a real release tag).One-time tag catch-up (done directly on the tags, not in this PR)
@v0created → v0.1.4, and the legacy@v1moved v0.1.1 → v0.1.4, so existing consumers aren't stranded 3 releases back.Deliberately NOT automated
No CI workflow force-advances the moving tags. A privileged auto-promotion of consumer-trusted aliases (
contents: write, triggered by any tag push, with no review) would expand attack surface and skip the reviewed-bump gate we hold ourselves to. Moving tags are advanced only inside a reviewed release.Relates to Ndevu12/stayAwakeBot#1229.
Closes #22