Skip to content

Fix release detection after npm registry timeouts - #69

Merged
eivindjonassen merged 1 commit into
mainfrom
fix/release-registry-timeout
Oct 22, 2026
Merged

eivindjonassen merged 1 commit into
mainfrom
fix/release-registry-timeout

Conversation

@eivindjonassen

Copy link
Copy Markdown
Member

Summary

Fixes the npm registry timeout in Follow OpenCode releases run #172.

The release detector previously exited after a single 30-second registry timeout. It now makes up to three attempts with exponential backoff for network errors, timeouts, HTTP 408/429, and server errors. Every attempt has a fresh timeout, including response-body reads. Permanent errors still fail immediately, with the package, requested version, attempt count, and underlying cause in the error.

Added CLI regression coverage for recovery, retry exhaustion, response cancellation, and failure without workflow outputs or upgrade-file edits.

Validation

  • Confirmed the timeout regression fails against the original script on Node 26.7.0.
  • All 12 release-script tests pass, including a rerun on this main-based branch.
  • Live registry lookup succeeds.
  • Full pnpm check, pnpm native:doctor, and pnpm check:public passed before moving the two-file fix onto current main.

@eivindjonassen
eivindjonassen merged commit 62917d0 into main Oct 22, 2026
2 checks passed
@eivindjonassen
eivindjonassen deleted the fix/release-registry-timeout branch October 22, 2026 08:45
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