Repository navigation
ci: make npm publish survive slow Rekor (sigstore 409 + 30s timeout) - #731
Merged
Merged
Conversation
Ports apify/crawlee#4323: patch [email protected] to fetch the existing Rekor entry on 409 and use a 30s timeout, and retry the publish step 5x with 60s waits.
B4nan
added
adhoc
janbuchar
approved these changes
Nov 7, 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.
The Oct 29 release failed in
lerna publishwithTLOG_CREATE_ENTRY_ERROR (409)after the versions were already tagged, so four versions never reached npm and every later release got blocked. This ports apify/crawlee#4323: a[email protected]patch with a 30s Rekor timeout that fetches the existing entry on a 409, and up to 5 publish attempts with 60s between them. Retrying is safe sincefrom-packageskips versions that are already on npm.