mirror of
https://github.com/openclaw/openclaw.git
synced 2026-07-14 11:26:13 +00:00
ef22e77f0b
The 2026.7.1 retro measured ~13h tag-to-published for beta.2 and stable 2026.6.11; any post-npm failure previously hard-aborted retries because the already-published guard refused the whole run. - resolve_openclaw_npm_publish_state replaces the abort guard: an already-published core version skips the core npm dispatch and resumes the remaining stages; verify_published_release still proves the registry state matches the tag before the page leaves draft. - Windows and Android promotion runs concurrently with the core npm publish (their only shared prerequisite is the draft release page, which is now created before the dispatch) and each promotion short-circuits when the release already carries its verified asset contract, so retries only redo failed stages. - The release proof cites the core npm run only when this run dispatched one; resumed publishes rely on the registry package check.