Yunare Maia 06b047a092 fix(release): extend npm propagation window and improve diagnostics (#943) ...

* fix(release): extend npm propagation window and improve diagnostics

The release verification step polls npm for up to 20 minutes (80 attempts
× 15s), but npm registry propagation can take longer. When the version
doesn't appear within the window, the workflow fails even though the
package was already published successfully.

Changes:
- Extend polling window from 20 to 30 minutes (120 attempts × 15s)
- Add --force flag to npm view to bypass cache on each poll
- Report full retry window in diagnostics (attempts × sleep time)
- Distinguish propagation delay from CLI verification failure in error message

Fixes #621

* fix(release): drop no-op --force from npm propagation polling

npm view --force is accepted but only prints a protections warning on a read-only command; --prefer-online already forces fresh registry metadata on each poll.

---------

Co-authored-by: morluto <76467478+morluto@users.noreply.github.com>

2026-10-08 00:26:25 +08:00

..

ISSUE_TEMPLATE

docs: improve GitHub issue and pull request templates

2026-08-29 10:11:21 +08:00

workflows

fix(release): extend npm propagation window and improve diagnostics (#943)

2026-10-08 00:26:25 +08:00

pull_request_template.md

refactor(build): generate MCP tool catalog at build time instead of committing it (#997)

2026-10-08 00:16:34 +08:00