docs: add v0.0.108 release entry - #8943
Conversation
Signed-off-by: prekshivyas <prekshiv@nvidia.com>
📝 WalkthroughWalkthroughThe changelog adds the v0.0.108 release entry. It documents onboarding, runtime, security, managed-image, contributor, and release-qualification changes. Changesv0.0.108 release documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Mergeability Score: 🔵 Low · up to The PR adds release notes only. One entry has an ambiguous product/profile description, and another documents scope that still needs owner confirmation; these are bounded documentation-accuracy follow-ups, so the PR is mergeable with explicit owner awareness. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
🌿 Preview your docs: https://nvidia-preview-pr-8943.docs.buildwithfern.com/nemoclaw |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/changelog/2026-08-12.mdx`:
- Line 16: Update the changelog sentence to clarify the compound modifier by
either describing it as a “managed vLLM profile for Muse Glimmer” when Muse
Glimmer is the profile name, or as a “Muse Glimmer-managed vLLM profile” when it
is the manager; preserve the rest of the sentence.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 9244624d-a84e-4794-8f72-f91825c15913
📒 Files selected for processing (1)
docs/changelog/2026-08-12.mdx
| NemoClaw validates each source, destination, and symlink boundary before mutation, persists accepted mounts for `rebuild` and interrupted `onboard --resume`, removes their declaration during `destroy`, and reports them in sandbox status. | ||
| For more information, refer to [Understand Sandbox State](/user-guide/openclaw/manage-sandboxes/state-and-backups/understand-sandbox-state) and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands). | ||
| Related change: [PR #8280](https://github.com/NVIDIA/NemoClaw/pull/8280). | ||
| - The explicit-only Experimental Muse Glimmer managed vLLM profile now runs on one DGX Spark with its validated checkpoint, ARM64 image, parser settings, and resource limits. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Clarify the compound modifier.
The phrase Muse Glimmer managed vLLM profile is ambiguous. If Muse Glimmer names the profile, use managed vLLM profile for Muse Glimmer. If it names the manager, use Muse Glimmer-managed vLLM profile.
Static analysis flags this compound modifier for hyphenation.
🧰 Tools
🪛 LanguageTool
[grammar] ~16-~16: Use a hyphen to join words.
Context: ... explicit-only Experimental Muse Glimmer managed vLLM profile now runs on one DGX...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/changelog/2026-08-12.mdx` at line 16, Update the changelog sentence to
clarify the compound modifier by either describing it as a “managed vLLM profile
for Muse Glimmer” when Muse Glimmer is the profile name, or as a “Muse
Glimmer-managed vLLM profile” when it is the manager; preserve the rest of the
sentence.
Source: Linters/SAST tools
PR Review Advisor — No blocking findings reportedAdvisor assessment: No blocking advisor findings reported Model lanes
Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests. 4 semantic terminology decisionsTerminology decisions are advisory. They affect the assessment only when a separate finding identifies concrete semantic impact.
E2E guidanceAdvisory only. A maintainer can dispatch the default E2E suite for the commit under review. Recommended E2E: None This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge. |
3 participants
Summary
Adds the canonical August 12, 2026 release entry for NemoClaw v0.0.108.
The entry accounts for all 55 merged PRs assigned to the release and unblocks the patch release plan and tag qualification.
Changes
docs/changelog/2026-08-12.mdxwith the parser-safe## v0.0.108heading.v0.0.108label with no missing, extra, or duplicate PR numbers.Type of Change
Quality Gates
Documentation Writer Review
docs-updateddocs/changelog/2026-08-12.mdxwas reviewed against the exact 55-PR release set,WRITING.md,docs/CONTRIBUTING.md, the controlled word list, and published-route rules.DGX Station Hardware Evidence
Verification
Signed-off-by:line and every commit appears asVerifiedin GitHubpre-commit,commit-msg, andpre-pushhooks passed, ornpm run validate:prpassed after refreshingorigin/mainwhen hooks were skipped or unavailablenpx vitest run test/changelog-docs.test.tspassed 6/6 tests on the final content.npm testfor broad runtime/test-harness changes;npm run checkfor repo-wide validation/coverage changes — command/result:npm run docsbuilds without warnings (doc changes only)Additional docs evidence:
npm run docscompleted successfully with zero errors; Fern reported two existing advisory warnings.The new canonical changelog page includes the required SPDX header and release heading; changelog pages do not use frontmatter.
Signed-off-by: prekshivyas prekshiv@nvidia.com
Summary by CodeRabbit