Skip to content

Wait up to 15 minutes for npm to list a published version - #40

Open
mattbaconz wants to merge 1 commit into
mainfrom
fix/npm-publish-verify-wait
Open

mattbaconz wants to merge 1 commit into
mainfrom
fix/npm-publish-verify-wait

Conversation

@mattbaconz

Copy link
Copy Markdown
Contributor

The publish runs for 0.25.2 (39743326274) and 0.26.0 (39926382276) both ended failed at "Verify npm version" although the package was published. The check polls npm view phonton-cli@<version> version 30 times, 10 seconds apart, so it gives up after 5 minutes. npm took longer than that to list both versions:

Version npm publish returned npm time[version] Delay
0.25.2 2026-10-22 07:50:39Z 07:57:51Z 7 min 12 s (during npm's degraded-publish incident)
0.26.0 2026-10-23 08:41:13Z 08:46:23Z 5 min 9 s

The 0.26.0 check made its last attempt at 08:46:20Z, 3 seconds before npm listed the version. It is not npm's local cache: a repeated npm view revalidates with the registry each time (cache revalidated in --loglevel http).

Change

  • Poll 90 times (about 15 minutes) instead of 30.
  • On timeout, print an error annotation saying npm accepted the publish and that a re-run stops at the already-published check, so the next step is checking npm view, not re-running.

Verified

  • The workflow parses as YAML, and the step script, run with bash -eo pipefail as Actions does, prints the version and exits 0 for a published version (0.26.0). With the loop shortened to 2 attempts and an unpublished version, it prints the waiting lines, the error annotation and npm's 404, and exits 1.
  • Not run: the workflow itself. A dispatch now would stop at "Confirm version is not already published" (0.26.0 is out), so the next release's publish run is the real test.

The publish runs for 0.25.2 and 0.26.0 both failed at "Verify npm version"
after a good publish. npm recorded 0.25.2 7 min 12 s and 0.26.0 5 min 9 s
after `npm publish` returned, and the check gave up after 5 minutes. Wait
up to 15 minutes, and say on timeout that the publish went through so a
re-run is not attempted blindly.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-23T09:45:26.273106Z d3d039b PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant