Skip to content

docs(changelog): follow up v0.0.106 release entry #8770

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jyaunches merged 2 commits into from
Aug 11, 2026
Merged

docs(changelog): follow up v0.0.106 release entry #8770

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
190bf88
docs(changelog): follow up v0.0.106 release entry
jyaunches Aug 11, 2026
66d93e1
Merge branch 'main' into codex/docs-v0.0.106-follow-up
cv Aug 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/changelog/2026-08-10.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ It also improves update safety, image defaults, and installation failure reporti

- `nemoclaw host probe --json`, onboarding, resume, and rebuild now use one credential-free readiness report and admission policy.
Blocking findings stop lifecycle effects before NemoClaw changes credentials, images, gateways, policies, or sandboxes.
Gateway readiness accepts OpenShell v0.0.101 `Server:` endpoint output and target-bound process tags only when trusted listener evidence matches the configured gateway.
It preserves the selected gateway's stale state when a gateway-scoped OpenShell status check cannot connect, so onboarding can reconcile the registered gateway.
For more information, refer to [System Readiness](/user-guide/openclaw/reference/system-readiness) and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
- The managed OpenShell runtime now uses v0.0.101 across installation, gateways, sandboxes, supervisors, and managed agent images.
Existing installations retain the v0.0.99 fallback only for migration, and incompatible sandbox names stop the update before destructive work.
Expand Down
Loading