This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
+12 more
Summary
AI summaryTimeouts for npm registry fetches increased from 3‑5 seconds to 10 seconds, fixing abort errors on cold start.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Bugfix | Medium |
Increased AbortSignal.timeout budgets from 5s and 3s to 10s in openclaw/src/index.ts. Increased AbortSignal.timeout budgets from 5s and 3s to 10s in openclaw/src/index.ts. Source: granite4.1:8b-q6_K@2026-05-19 Confidence: high |
— |
| Bugfix | Medium |
Removed abort message race condition for slow-but-eventually-succeeding fetches. Removed abort message race condition for slow-but-eventually-succeeding fetches. Source: granite4.1:8b-q6_K@2026-05-19 Confidence: high |
— |
| Bugfix | Medium |
Ensures /hivemind_version command completes within 10s even during cold start. Ensures /hivemind_version command completes within 10s even during cold start. Source: granite4.1:8b-q6_K@2026-05-19 Confidence: high |
— |
| Bugfix | Medium |
Eliminated abort message race for slow-but-eventually-succeeding auto-update checks at startup. Eliminated abort message race for slow-but-eventually-succeeding auto-update checks at startup. Source: granite4.1:30b@2026-05-19-audit Confidence: high |
— |
Full changelog
Fixes #105 and #109.
Why
Two AbortSignal.timeout budgets in openclaw/src/index.ts are aggressive enough to abort the npm-registry fetch on cold gateway init:
- Line 192 —
checkForUpdateat startup (5s) - Line 694 —
/hivemind_versionslash command (3s)
Steady-state response time from registry.npmjs.org/@deeplake/hivemind/latest is ~170ms. The aborts happen during cold start when this fetch runs concurrently with plugin discovery, Bonjour watchdogs, and TLS warm-up. Both issues track this same root cause.
Observed live on the user's gateway 2026-05-12T20:49:48 right after a systemctl --user restart openclaw-gateway:
[plugins] Auto-update check failed: The operation was aborted due to timeout
The expected ⬆️ Hivemind update available: <current> → <latest>. Run: hivemind update notice never renders for that gateway run, so users miss the upgrade prompt until the next restart hits a warm cache.
What changed
Bumped both timeouts to 10s (~60x headroom over observed steady-state latency).
- The startup site is fire-and-forget (
checkForUpdate(logger).catch(() => {})at the bottom ofregister()), so a longer budget does not add session-start latency. Per the team's "no session-start latency" rule, the network call is intentionally unawaited; the only effect of a longer timeout is "the abort message no longer races a slow-but-eventually-succeeding fetch." - The
/hivemind_versionsite is a user-invoked command — 10s is well below user-patience threshold and matches the worst cold-start latency we want to cover.
Tests
npm run typecheck— cleannpm test— 2380/2380 passing- Source-only change; CI regenerates
openclaw/dist/.
Test plan
- [ ] After this lands and a release publishes, on a cold openclaw gateway:
journalctl --user -u openclaw-gateway -e | grep 'Auto-update check'should show no "operation was aborted due to timeout" lines. - [ ] Run
/hivemind_versionfrom inside the agent. Should return theUpdate available / up to datemessage, not "Could not check for updates."
Summary by CodeRabbit
- Bug Fixes
- Improved reliability of version checks and auto-update detection to better handle varying network conditions.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Track Hivemind turns agent traces into skills and shares with your team
Get notified when new releases ship.
Sign up freeAbout Hivemind turns agent traces into skills and shares with your team
All releases →Related context
Related tools
Earlier breaking changes
- v0.7.52 Removes `hivemind tasks` CLI and related code surfaces.
- v0.7.51 Removes `hivemind tasks` CLI and related code surfaces.
- v0.7.19 Module name skilify replaced with skillify; affects all imports
- v0.7.19 CLI command skilify removed; renamed to skillify without deprecation alias
- v0.7.18 CLI subcommand renamed from `skilify` to `skillify`; no deprecation alias.
Beta — feedback welcome: [email protected]