From 6021fc6f3f3977e9178fb9e6d8154fba3edf4947 Mon Sep 17 00:00:00 2001 From: Julie Yaunches Date: Mon, 20 Jul 2026 17:48:58 -0400 Subject: [PATCH] docs: add v0.0.90 release changelog Signed-off-by: Julie Yaunches --- docs/changelog/2026-07-20.mdx | 17 +++++++++++++++++ docs/reference/commands.mdx | 4 ++-- 2 files changed, 19 insertions(+), 2 deletions(-) diff --git a/docs/changelog/2026-07-20.mdx b/docs/changelog/2026-07-20.mdx index 5ce295b5a5..cea2e614c0 100644 --- a/docs/changelog/2026-07-20.mdx +++ b/docs/changelog/2026-07-20.mdx @@ -3,6 +3,23 @@ * SPDX-License-Identifier: Apache-2.0 */} +## v0.0.90 + +NemoClaw v0.0.90 keeps managed-image routing identifiers out of secret-shaped build arguments, restores provider-reset recovery, corrects WhatsApp health reporting, and aligns DGX Station guidance with the versioned installer. + +- Managed OpenClaw, Hermes, and Deep Agents images now use `NEMOCLAW_INFERENCE_PROVIDER_ID` for the non-secret inference route selector, while provider credentials stay in OpenShell storage and the host-side credential alias remains unchanged. + Existing custom images can use the legacy selector through v0.0.90 and should migrate before the fallback is removed in v0.0.91. + For more information, refer to the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands). +- `credentials reset` now recognizes sandbox attachments from wrapped OpenShell diagnostics, validates each sandbox name, detaches affected sandboxes, and retries provider deletion without exposing credential values. + For more information, refer to [Credential Rotation](/user-guide/openclaw/security/credential-rotation). +- OpenClaw WhatsApp status now recognizes the current paired-session path and derives in-process bridge activity from redacted gateway-log evidence. + This prevents a working paired channel from being reported as unpaired or inactive while keeping phone numbers and raw log lines out of host output. + For more information, refer to [Set Up WhatsApp](/user-guide/openclaw/manage-sandboxes/messaging-channels/set-up-whatsapp) and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands). +- DGX Station coding-agent guidance now delegates qualification, preparation, consent, and resume behavior to the selected versioned installer. + Station Express keeps Nemotron 3 Ultra 550B as the default, while `--station-deepseek` selects DeepSeek V4 Flash. + Related guidance adds bounded OpenIB repair or disable steps, clarifies legacy recovery state limits, and gives platform-specific setup its own navigation group. + For more information, refer to [Prepare DGX Station to Install NemoClaw](/user-guide/openclaw/get-started/additional-setup/dgx-station-preparation), the [NemoClaw Quickstart with OpenClaw](/user-guide/openclaw/get-started/quickstart), and [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes). + ## v0.0.89 NemoClaw v0.0.89 broadens qualified DGX Station installation paths, preserves inference choices through onboarding and rebuilds, strengthens sandbox recovery, discloses messaging policy scope before mutation, and keeps CLI output and background processes contained. diff --git a/docs/reference/commands.mdx b/docs/reference/commands.mdx index 81f840ece8..83bbe24e02 100644 --- a/docs/reference/commands.mdx +++ b/docs/reference/commands.mdx @@ -690,9 +690,9 @@ All NemoClaw build arguments (`NEMOCLAW_MODEL`, `NEMOCLAW_INFERENCE_PROVIDER_ID` `NEMOCLAW_INFERENCE_PROVIDER_ID` is a non-secret inference route identifier (for example `inference` for proxied providers, or a provider family such as `openai`), never a credential; provider credentials stay in OpenShell provider storage. It replaces the former `NEMOCLAW_PROVIDER_KEY` image argument, whose secret-shaped name triggered a BuildKit `SecretsUsedInArgOrEnv` warning. The host-side `NEMOCLAW_PROVIDER_KEY` credential alias is unchanged; this migration only renames the managed image route selector. -Custom Dockerfiles that declare either `ARG NEMOCLAW_INFERENCE_PROVIDER_ID` or the legacy `ARG NEMOCLAW_PROVIDER_KEY` keep working through v0.0.89. +Custom Dockerfiles that declare either `ARG NEMOCLAW_INFERENCE_PROVIDER_ID` or the legacy `ARG NEMOCLAW_PROVIDER_KEY` keep working through v0.0.90. NemoClaw updates whichever supported declaration is present, and runtime consumers read the legacy name as a fallback. -Rename the legacy `ARG`/`ENV` declaration to `NEMOCLAW_INFERENCE_PROVIDER_ID` before legacy support is removed in v0.0.90. +Rename the legacy `ARG`/`ENV` declaration to `NEMOCLAW_INFERENCE_PROVIDER_ID` before legacy support is removed in v0.0.91. Custom Dockerfiles must declare `ARG NEMOCLAW_TOOL_DISCLOSURE=progressive` exactly once in the final build stage and promote it into that stage's runtime environment. The usual runtime contract is: