Skip to content

Time out a stuck npm publish and log its authentication - #4

Merged
Inchill merged 2 commits into
mainfrom
ci/release-diagnostics
Oct 22, 2026
Merged

Inchill merged 2 commits into
mainfrom
ci/release-diagnostics

Conversation

@Inchill

@Inchill Inchill commented Oct 22, 2026 •

Copy link
Copy Markdown
Owner

The release job's publish step hangs after the provenance statement is published. On the last run the registry answered the publish request with E503 Service Unavailable after about 12 minutes, and 1.1.1 never reached npm. Authentication is not the problem (it failed with a 404 before Trusted Publishing was set up), and npm's status page shows no incident.

Changes

  • timeout-minutes: 20 on the publish step, so a stuck publish fails instead of holding the runner for hours, while still leaving room to log the registry's response.
  • Prints npm --version before publishing (Trusted Publishing needs 11.5.1 or later).
  • npm publish --loglevel verbose, which logs the Trusted Publishing token exchange and each registry request, so the next run shows how long the registry takes and what it returns.
  • Closes stdin (< /dev/null), so npm cannot sit waiting for input such as a one-time password prompt.

No version change: merging this runs the release again for 1.1.1, which is still unpublished.


Generated by Claude Code

The publish step could wait indefinitely after signing provenance, with nothing
in the log to say why. It now fails after 10 minutes, prints the npm version,
publishes with verbose logging so the Trusted Publishing token exchange and the
registry requests show up, and closes stdin so npm cannot wait for input.
The registry answered a stuck publish with 503 after about 12 minutes; a
20-minute limit lets the verbose log capture that response.
@Inchill
Inchill merged commit 3c4d446 into main Oct 22, 2026
1 check passed
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