docs: prepare v0.0.120 release - #11100
Merged
Merged
Conversation
cjagwani
added
area: docs
Contributor
|
🌿 Preview your docs: https://nvidia-preview-pr-11100.docs.buildwithfern.com/nemoclaw |
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe pull request adds the v0.0.120 changelog and documents Hermes sandbox rebuild behavior when no base-image hint or override exists. ChangesRelease and sandbox documentation
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to This updates the v0.0.120 changelog and Hermes recovery guidance without changing runtime behavior. The documented recovery safeguards align with the existing implementation, and no current merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Contributor
|
PR Review Advisor finished for commit |
prekshivyas
approved these changes
Sep 5, 2026
cjagwani
added a commit
that referenced
this pull request
Sep 5, 2026
<!-- markdownlint-disable MD041 --> ## Outcome Clarifies that `NEMOCLAW_HERMES_SANDBOX_BASE_IMAGE_REF` applies to both Hermes onboarding and rebuild. The legacy Hermes recovery guidance now names the override and preserves its official-repository, immutable-digest constraints. ## Reason The PR Review Advisor on #11100 correctly found that the recovery page mentioned an explicit image override while the commands reference still described that override as onboarding-only. The implementation reads the same variable during rebuild before deciding whether the legacy release-pinned base is required. ### Related issues Follow-up to #11100 ## Changes - Document the Hermes base-image override as an onboarding and rebuild input. - Name the override in the legacy recovery condition and link the Hermes commands reference. - Keep the guidance scoped to Hermes and retain the official remote repository and trusted immutable digest requirements. ## Verification - `npx vitest run --project integration test/generation/check-docs-links.test.ts test/generation/check-docs-published-routes.test.ts test/generation/post-merge-docs.test.ts` — 3 files and 125 tests passed. - `npm run docs` — passed with 0 errors and 5 existing Fern warnings. - Independent documentation audit — approved the repair as source-accurate, Hermes-scoped, and publication-safe. - Normal `pre-commit`, `commit-msg`, and `pre-push` hooks — passed. - `git diff --check` — passed. - GitHub commit verification — `396dbd300e26909589a54cdfc803103082d8ed9e` is Verified with reason `valid`. - Secret review — the diff contains no secrets, API keys, or credentials. ## Review notes This is the complete disposition of the one valid Advisor finding on the merged release-docs PR #11100. All other Advisor specialists and CodeRabbit reported no issue. --- Signed-off-by: Charan Jagwani <cjagwani@nvidia.com> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Documentation** - Clarified that the Hermes sandbox base-image override applies during both onboarding and rebuild. - Documented fallback behavior when no image hint or override is provided. - Clarified that overrides must use the official remote repository and a trusted immutable digest. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Adds the canonical dated documentation entry for v0.0.120 and records the release's material user-facing changes before tag planning. The Hermes rebuild guide now also documents the fail-closed immutable-base requirement for legacy sandboxes without an image hint.
Reason
Release planning requires a merged
docs/changelog/2026-09-04.mdxcontaining exactly one## v0.0.120heading. The existing automation draft does not contain that required changelog and does not cover the full release scope, so this PR provides a fresh, independently reviewed release-docs update.Related issues
Relates to #10919
Changes
Verification
npx vitest run --project integration test/generation/check-docs-links.test.ts test/generation/check-docs-published-routes.test.ts test/generation/post-merge-docs.test.ts— 3 files and 125 tests passed.npm run docs— passed with 0 errors and 5 existing Fern warnings.v0.0.119..origin/main, validated all 29 PR links and published routes, and found no unsupported product claims or remaining corrections.pre-commit,commit-msg, andpre-pushhooks — passed.git diff --check— passed.a22fe0989fd72c7daaa9b2e7a4734a3edc069abais Verified with reasonvalid.Review notes
The existing automation draft #10919 is intentionally left untouched. This PR supersedes its release-docs content with the complete canonical changelog and a variant-correct Hermes recovery update.
Signed-off-by: Charan Jagwani cjagwani@nvidia.com
Summary by CodeRabbit