Repository navigation
fix(re0-release): re-cut a tag the author broke at the same version - #22
Merged
Merged
Conversation
…ward - re0-release and AGENTS.md delete and re-cut a tag whose message, signature or target the author got wrong at the same version, and move the version on only when a published artifact is wrong; the rule against hand-running workflow steps no longer lists moving a tag - tagging confirms git tag -v reports a good signature before the push, the check a tag message without a trailing newline fails
LilMGenius
force-pushed
the
release/0.17.7
branch
from
September 30, 2026 22:52
631bf64 to
7d5dc62
Compare
LilMGenius
changed the title
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
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.
When the author cuts a tag wrong, the release checklist moved the version forward, so a published version number could carry no artifact and the broken tag stayed in history.
Failing input: a signed tag whose message lacks a trailing newline, as v0.17.6 did;
git tag -vreports no signature and the release notes lose the install command.Cause:
re0-releaseand AGENTS.md had no rule for a tag the author broke, and the rule against hand-running workflow steps listed moving a tag, which left rolling forward as the only path (#21).Evidence
git tag -vbefore the pushFix and scope
skills/depth/re0-release/SKILL.mdand AGENTS.md now delete and re-cut a tag whose message, signature or target the author got wrong, and move the version on only when a published artifact is wrong. Tagging confirmsgit tag -vreports a good signature before the push.package.jsonandpackage-lock.jsonmove to 0.17.7, which ships #20.Supersedes #21.