Repository navigation
release 0.32.1: the A0 content under a version npm will take - #31
Merged
Merged
Conversation
v0.32.0 is a git tag with no package. The release run on it was green up to
the publish, and the publish was refused by npm's transparency log:
npm error code TLOG_CREATE_ENTRY_ERROR
npm error error creating tlog entry - (409) an equivalent entry already
exists in the transparency log
The registry confirms nothing was served: @macula-io/ts has no 0.32.0 version,
no dist-tag and no time entry. Sigstore refuses a second entry for the same
subject, so re-running the same tarball cannot work — the version has to move.
So this is the same content, unchanged, under 0.32.1: package.json and both
version fields of package-lock.json, and the changelog section retitled and
dated 2026-10-29 with one plain line saying what happened to 0.32.0 and that
nothing was ever served for it. The v0.32.0 tag is untouched.
Registry checked before review, not after: tag v0.32.1 is free and
registry.npmjs.org answers 404 for @macula-io/ts 0.32.1, while the same
endpoint answers 200 for 0.31.0.
Raf's ruling, 2026-10-29: ts goes out as 0.32.1.
Co-Authored-By: Claude Code <noreply@anthropic.com>
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.
Refs the 29 Oct release batch.
Purpose (reliability): the A0 work reaches npm users at all — 0.32.0 never will, because npm's transparency log refuses to mint a second entry for it.
Why 0.32.1 and not the tag we have
v0.32.0is cut and pushed on 7ee977e. Its release run 40803212492 was green through guard, release guard, advisories, test, docs and all five prebuilds, then failed atpublish to npm:The registry confirms nothing was served:
@macula-io/tshas no0.32.0, no dist-tag pointing at it and notimeentry. The 409 is deterministic — Sigstore will refuse the same subject again — so the version has to move. Thev0.32.0tag stays exactly where it is.This PR
package.jsonand both version fields ofpackage-lock.json: 0.32.1.CHANGELOG.md: the section is retitled## [0.32.1] - 2026-10-29, content unchanged, with one plain line saying 0.32.0 exists only as a git tag, that npm refused it and that nothing was ever served for it.Registry check, before review
v0.32.1does not exist locally or on origin;registry.npmjs.org/@macula-io/ts/0.32.1answers 404, and the same endpoint answers 200 for 0.31.0 (positive control: the method finds a version that does exist).Raf's ruling, 2026-10-29: ts goes out as 0.32.1, tag after green main CI.
🤖 Generated with Claude Code