ci: allow npm registry processing before verification - #61
Merged
Merged
Conversation
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: ci: allow npm registry processing before verification This is item 1/1 in the current shard. Shard 0/1. This temporary status tracks the active review worker. The completed review will appear in the durable ClawSweeper review comment. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
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
1 participant
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 v0.2.0 publish succeeded with signed provenance, but npm reported asynchronous processing and the release workflow exhausted its one-minute visibility check before the version could be read. Extend registry and dist-tag polling to 60 attempts at ten-second intervals in both release workflows. Keep the existing integrity checks and fail when the bounded window expires.
This changes CI timing only and does not replace the published tag or package. Workflow lint and independent Codex review through P2 passed. The repository’s npm packaging checks run on AWS Crabbox before merge; the captured live release failure provides the reproduction.
Final remote validation passed: 23 npm-wrapper, package-builder, and release-note tests, plus the universal npm package build/install/CLI smoke. Registry metadata subsequently appeared at 10:07:04 UTC, over six minutes after npm accepted the upload, confirming that the former one-minute window was insufficient.