Skip to content

fix(release): roll the release forward past an unverifiable v0.17.6 tag - #21

Closed
LilMGenius wants to merge 1 commit into
mainfrom
release/0.17.7
Closed

LilMGenius wants to merge 1 commit into
mainfrom
release/0.17.7

Conversation

@LilMGenius

@LilMGenius LilMGenius commented Sep 30, 2026 •

Copy link
Copy Markdown
Owner

Superseded by #22, which deletes and re-cuts the broken tag at the same version instead of moving the version on.

The v0.17.6 tag could not be verified: its message ended without a newline, so the signature was appended to its last line.

Failing input: git tag -v v0.17.6.
Cause: the tag message file lacked a trailing newline, so git tag -s -F glued the signature onto the install line.

Evidence

input observed on v0.17.6
git tag -v v0.17.6 no signature reported
release workflow notes filter would drop the install command from the release notes

Fix and scope

This bumped package.json and package-lock.json to 0.17.7 so the frontmatter gate from #20 would ship under a clean signed tag, leaving the defective tag in place. Closed unmerged in favour of #22.

- v0.17.6 carried its signature glued to the last line of its message, so git could not verify it and the release workflow would have cut the install command from the notes; 0.17.7 ships the same change under a clean tag
@LilMGenius LilMGenius closed this Sep 30, 2026
@LilMGenius
LilMGenius deleted the release/0.17.7 branch September 30, 2026 22:40
@LilMGenius LilMGenius changed the title fix: roll the release forward past an unverifiable v0.17.6 tag fix(release): roll the release forward past an unverifiable v0.17.6 tag Oct 24, 2026
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