Skip to content

docs: add v0.0.100 release entry - #8030

Merged
senthilr-nv merged 1 commit into
mainfrom
codex/docs-v0.0.100-release-entry
Aug 1, 2026
Merged

docs: add v0.0.100 release entry#8030
senthilr-nv merged 1 commit into
mainfrom
codex/docs-v0.0.100-release-entry

Conversation

@senthilr-nv

@senthilr-nv senthilr-nv commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds the canonical dated changelog entry for v0.0.100 so the maintainer release plan can verify the pre-tag documentation prerequisite. The entry summarizes the user-facing changes merged since v0.0.99 and links to the relevant guides.

Changes

  • Add docs/changelog/2026-07-31.mdx with the exact ## v0.0.100 heading.
  • Cover restored OpenClaw pairing, transactional replacement, Deep Agents Code, onboarding recovery, lifecycle cleanup, Hermes builds, host provenance, documentation, and trusted E2E evidence.
  • Distinguish active Docker and Kubernetes runtime-bundle enforcement from the still-inactive managed shared-state transaction foundation.

Source Coverage

The release entry maps the doc-impacting merged PRs in the v0.0.99..main release range to docs/changelog/2026-07-31.mdx: #8021, #8024, #7973, #8028, #7947, #7788, #7884, #8023, #7969, #8020, #7989, #8000, #7907, #7942, #7567, #8013, #7955, #8017, #8014, #8015, #7629, #7644, #7821, #7971, and #7991.

PR #7974 was reviewed after the final rebase and excluded because it changes internal maintainer-skill attribution policy and tests only; it does not change a user-facing product or documentation surface.

Type of Change

  • Code change (feature, bug fix, or refactor)
  • Code change with doc updates
  • Doc only (prose changes, no code sample modifications)
  • Doc only (includes code sample changes)

Quality Gates

  • Tests added or updated for changed behavior
  • Existing tests cover changed behavior — justification: the changelog contract test validates the dated entry, version heading, SPDX form, and route constraints.
  • Tests not applicable — justification:
  • Docs updated for user-facing behavior changes
  • Docs not applicable — justification:
  • Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
  • Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification:
  • Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Documentation Writer Review

  • Documentation writer subagent reviewed the completed changes
  • Result: docs-updated
  • Evidence: docs/changelog/2026-07-31.mdx; exact-head review passed for 6093f44f; writing rules and documentation style reviewed; npx vitest run test/changelog-docs.test.ts passed 6/6; npm run docs passed with zero Fern errors and two generic Fern upgrade notices.
  • Agent: Codex Desktop

DGX Station Hardware Evidence

  • Tested on DGX Station
  • Tested commit: Not applicable; no DGX Station host script changed.
  • Station profile/scenario: Not applicable.
  • Result: Not applicable.
  • Supporting evidence: Not applicable.

Verification

  • PR description includes a Signed-off-by: line and every commit appears as Verified in GitHub
  • Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run validate:pr passed after refreshing origin/main when hooks were skipped or unavailable
  • Targeted behavior tests pass for the current change set, or tests are marked not applicable above — command/result or justification: npx vitest run test/changelog-docs.test.ts passed 6/6 at 6093f44f.
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result: Not applicable to a dated prose-only release entry.
  • Quality Gates section completed with required justifications or waivers
  • No secrets, API keys, or credentials committed
  • npm run docs builds without warnings (doc changes only) — validation passed with zero errors; Fern emitted two generic upgrade notices.
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only) — the changelog entry has the required parser-safe MDX SPDX header; dated changelog entries intentionally do not use page frontmatter.

Signed-off-by: Senthil Ravichandran senthilr@nvidia.com

Summary by CodeRabbit

  • Documentation
    • Added release notes for v0.0.100.
    • Documented improvements to restore pairing, sandbox replacement, onboarding recovery, lifecycle cleanup, runtime handling, build support, host readiness, and end-to-end validation.

Signed-off-by: Senthil Ravichandran <senthilr@nvidia.com>
@senthilr-nv senthilr-nv added area: docs Documentation, examples, guides, or docs build v0.0.100 labels Aug 1, 2026
@senthilr-nv senthilr-nv self-assigned this Aug 1, 2026
@coderabbitai

coderabbitai Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The PR adds the v0.0.100 changelog. It documents sandbox restoration, runtime handling, onboarding recovery, lifecycle cleanup, Hermes validation, readiness provenance, documentation, and trusted E2E validation.

Changes

Release documentation

Layer / File(s) Summary
v0.0.100 changelog entry
docs/changelog/2026-07-31.mdx
Adds release notes for sandbox safety, Deep Agents Code runtime handling, onboarding recovery, lifecycle cleanup, Hermes builds, readiness provenance, runtime foundations, documentation, and validation.

Estimated code review effort: 2 (Simple) | ~5 minutes

Possibly related PRs

  • NVIDIA/NemoClaw#7077: Documents overlapping Hermes build and runtime validation changes.
  • NVIDIA/NemoClaw#7873: Adds a changelog entry covering overlapping Hermes, Deep Agents Code, readiness, recovery, and lifecycle changes.

Suggested reviewers: cv

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the addition of the v0.0.100 changelog entry.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/docs-v0.0.100-release-entry

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

@senthilr-nv
senthilr-nv requested review from apurvvkumaria and cv August 1, 2026 01:32

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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-07-31.mdx`:
- Around line 1-4: Replace the JSX comment wrapping the SPDX header at the
beginning of the MDX file with an HTML comment, preserving the existing
copyright and license text exactly.
🪄 Autofix (Beta)

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: 89f00df1-9519-46ce-afa1-d9680bcf8de7

📥 Commits

Reviewing files that changed from the base of the PR and between 4feccff and 6093f44.

📒 Files selected for processing (1)
  • docs/changelog/2026-07-31.mdx

Comment on lines +1 to +4
{/*
* SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
* SPDX-License-Identifier: Apache-2.0
*/}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟠 Major | ⚡ Quick win

Use an HTML comment for the SPDX header.

This MDX file uses a JSX comment, but the repository requires HTML comments for SPDX headers in Markdown and MDX files. Replace lines 1-4 with an HTML comment.

As per coding guidelines, every source file must include the appropriate SPDX header, and Markdown and MDX files must use HTML comments for SPDX headers.

Proposed fix
-{/*
- * SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
- * SPDX-License-Identifier: Apache-2.0
- */}
+<!--
+SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+SPDX-License-Identifier: Apache-2.0
+-->
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
{/*
* SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
* SPDX-License-Identifier: Apache-2.0
*/}
<!--
SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
SPDX-License-Identifier: Apache-2.0
-->
🤖 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-07-31.mdx` around lines 1 - 4, Replace the JSX comment
wrapping the SPDX header at the beginning of the MDX file with an HTML comment,
preserving the existing copyright and license text exactly.

Source: Coding guidelines

@senthilr-nv
senthilr-nv merged commit 227e8b9 into main Aug 1, 2026
66 of 67 checks passed
@senthilr-nv
senthilr-nv deleted the codex/docs-v0.0.100-release-entry branch August 1, 2026 01:34
@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — No blocking findings reported

Advisor assessment: No blocking advisor findings reported
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions

Model lanes

  • GPT-5.6 Terra (primary): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
  • Nemotron 3 Ultra (second opinion): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
  • Model comparison: normalized findings match; normalized E2E selections match; severity counts match.

Second-opinion E2E selections are advisory. They do not change the primary assessment or E2E / PR Gate.

E2E guidance

Advisory only. E2E / PR Gate selects and runs jobs independently.

Recommended E2E: None

Workflow run details

This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Documentation, examples, guides, or docs build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants