Repository navigation
fix(release): retry failed package publishing - #5271
Merged
Merged
Conversation
Sigstore transparency log intermittently answers TLOG_CREATE_ENTRY_ERROR (409) during provenance publishing, which fails the release. Retry lerna publish from-package up to 5 times; versions already on npm are skipped. If every attempt fails, publish the remaining packages without provenance. Drop --concurrency 1, which did not address the cause. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
glowcloud
approved these changes
Oct 21, 2026
This was referenced Oct 21, 2026
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.
Problem
Release runs fail with
TLOG_CREATE_ENTRY_ERROR (409) an equivalent entry already exists in the transparency logwhile publishing with provenance. Different packages fail in each run, and--concurrency 1(#5270) did not prevent it, so the cause is not parallel publishing.Changes
lerna publish from-packageup to 5 times with a 30s pause. Versions already on npm are skipped, so only failed packages are republished.publishConfig.provenanceis flipped in the CI checkout only) so a release is never left half-published. A warning annotation is emitted.--concurrency 1, which did not address the cause.Notes
lerna publish from-packagenot requiring a clean working tree.🤖 Generated with Claude Code