Skip to content

fix: verify existing release tags before creation#13

Merged
sarveshsea merged 2 commits into
mainfrom
fix/read-first-release-tag
Jul 16, 2026
Merged

fix: verify existing release tags before creation#13
sarveshsea merged 2 commits into
mainfrom
fix/read-first-release-tag

Conversation

@sarveshsea

@sarveshsea sarveshsea commented Jul 16, 2026

Copy link
Copy Markdown
Member

Summary

  • reproduce the protected-tag recovery failure in the workflow contract
  • read and validate an existing immutable tag before attempting Git ref creation
  • preserve atomic creation, exact SHA checks, 404-only creation, and 422 race recovery

Test plan

  • node scripts/check-release-workflows.mjs (RED before workflow fix, GREEN after)
  • node --test tests/release-supply-chain.test.mjs
  • npm run verify

Live context

The exact protected v5.1.0 tag already resolves to reviewed release commit c26ad054f999ea726eb29c93d75e5a0dd8a7ea7e. This makes the final GitHub release job safely recoverable without asking the workflow token to recreate that tag.


View with Codesmith Autofix with Codesmith
Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.

@sarveshsea
sarveshsea merged commit 195c74e into main Jul 16, 2026
4 checks passed
@sarveshsea
sarveshsea deleted the fix/read-first-release-tag branch July 16, 2026 18:55
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