fix(ci): retry real install paths in verify-publish#719
Merged
khaliqgant merged 4 commits intomainfrom Apr 11, 2026
Merged
Conversation
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
The script was committed with mode 100644 but is invoked directly as a command in the workflow, requiring the executable bit. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The verify-publish workflow failed because @relaycast/sdk was not properly installed during global installs. Root cause: version conflict between root dependency (pinned "1.0.0") and bundled @agent-relay/sdk (needs "^1.1.0") caused npm to create empty placeholder directories with no package.json or dist/ files. - Update @relaycast/sdk from "1.0.0" to "^1.1.0" to resolve conflict - Add @relaycast/sdk to bundledDependencies for reliable tarball inclusion Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Address Devin review: the Docker verification job runs npm install without retry logic, and retry-command.sh was not copied into the Docker image. This creates a race condition where registry metadata is available but the tarball isn't yet on the CDN. - Copy retry-command.sh into Docker image - Wrap global and local npm install calls with retry-command.sh Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
2 participants
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.
Summary
Why
verify-publish.ymlwas changed to usenpm cache addas a propagation gate. That fixed one class of false positives, but introduced a new false negative: publish can succeed while some runners still fail the preflight because a CDN edge lags. In that case the workflow fails before the actual install tests even run.This patch keeps a lightweight metadata wait via
npm view, then adds retries to the real install operations we actually care about:That makes the workflow verify user-facing installability without making transient npm propagation lag look like a publish failure.
Testing