Repository navigation
release: npm verify waits up to 10 minutes for propagation - #110
Merged
Merged
Conversation
github-actions
Bot
added
agent:reviewed-clean
🔎 Codex cross-audit (agent:audit)Blocking: none. Findings: none. The PR only extends the npm registry visibility wait in Checks: |
Merged
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.
v0.5.2's npm job published all seven packages with provenance, then its verify step failed:
npm view @dshakesnotbot/halo@0.5.2was still 404 after the 60 s retry window (the first version of a new package took longer to appear). The packages were live minutes later (npx @dshakesnotbot/halo@0.5.2 version-> 0.5.2). Wait up to 10 minutes (60 x 10 s). actionlint clean.