Repository navigation
Fix provenance 409 - #2755
Merged
Merged
Fix provenance 409#2755
Conversation
- Root cause: npm provenance uploads a signed entry to Sigstore's Rekor log with a 5s timeout. Rekor has been slow, so the client timed out after Rekor had stored the entry, resent it, got 409 "equivalent entry already exists", and `sigstore` (hard-coded `fetchOnConflict: false`) failed the publish: v7.4.25 published only tldts-utils and tldts-tests. - Fix: patch sigstore 5.0.1 (used by lerna's libnpmpublish) to fetch the existing entry on conflict (it is ours: same signature and ephemeral key, so provenance stays valid) and to wait 30s instead of 5s, since that fetch hits the same slow Rekor. Drop once sigstore-js#1791 ships.
- Root cause: npm has no multi-package transaction, so a failure mid-publish leaves an already-pushed version partly on npm, with nothing to finish it. - Fix: if publishing fails, run `lerna publish from-package` once more (it publishes only the missing packages), only when this run made the release commit (HEAD != GITHUB_SHA), HEAD is tagged with lerna's version, and HEAD is on origin/master. The manifests are restored first (a failed publish leaves lerna's `gitHead` in them, which `from-package` rejects), so the bytes match the tag; the release concurrency group keeps a newer release from running in between. If the retry fails too, cut a new version.
remusao
force-pushed
the
fix-provenance-409
branch
from
November 12, 2026 12:10
3d36fcb to
c5dcfb4
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
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.
No description provided.