[GH-ISSUE #621] Release verification can fail before npm package propagation completes #298

Closed
opened 2026-10-15 18:23:37 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @morluto on GitHub (Oct 5, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/621

Summary

The 2026-10-05 release run for rea-agents 4.0.0 successfully completed npm publish, but the follow-up verification failed because npm did not expose the version during the workflow's five-minute polling window. The package is visible on npm now.

Failing run: https://github.com/morluto/rea/actions/runs/37356342944

Impact

The Release workflow reports failure after the package has already been published. Since MCP Registry publication depends on the npm job succeeding, that follow-up publication is skipped.

Proposed fix

Extend the bounded registry visibility window and request fresh metadata on each poll, while keeping CLI verification after the version appears. Report the full retry window in diagnostics so future failures distinguish propagation delay from CLI verification failure.

Originally created by @morluto on GitHub (Oct 5, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/621 ## Summary The 2026-10-05 release run for rea-agents 4.0.0 successfully completed npm publish, but the follow-up verification failed because npm did not expose the version during the workflow's five-minute polling window. The package is visible on npm now. Failing run: https://github.com/morluto/rea/actions/runs/37356342944 ## Impact The Release workflow reports failure after the package has already been published. Since MCP Registry publication depends on the npm job succeeding, that follow-up publication is skipped. ## Proposed fix Extend the bounded registry visibility window and request fresh metadata on each poll, while keeping CLI verification after the version appears. Report the full retry window in diagnostics so future failures distinguish propagation delay from CLI verification failure.
bsakaguchi 2026-10-15 18:23:37 +00:00
  • closed this issue
  • added the
    bug
    label
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#298
No description provided.