Skip to content

docs(release): correct v0.0.75 release notes#6372

Merged
ericksoa merged 1 commit into
mainfrom
docs/fix-v0075-release-notes-accuracy
Jul 7, 2026
Merged

docs(release): correct v0.0.75 release notes#6372
ericksoa merged 1 commit into
mainfrom
docs/fix-v0075-release-notes-accuracy

Conversation

@ericksoa

@ericksoa ericksoa commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Correct the v0.0.75 release-note entry merged in #6371 before the release tag is cut.
This follow-up restores the omitted OpenClaw 2026.6.10 upgrade and narrows three claims to the runtime contracts that actually shipped.

Changes

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:
  • Tests not applicable — justification: prose-only release-note corrections with no runtime behavior or code samples.
  • 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:

Verification

  • PR description includes the DCO sign-off declaration and every commit appears as Verified in GitHub
  • Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run check:diff passed 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: tests are not applicable; npm run docs passed with 0 errors and 2 pre-existing warnings.
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result:
  • 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) — result: 0 errors and 2 pre-existing warnings (missing authenticated redirects check and existing light-theme accent contrast).
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Aaron Erickson aerickson@nvidia.com

Summary by CodeRabbit

  • Documentation
    • Updated the v0.0.75 release notes with clearer wording and expanded details.
    • Added more specific notes about the runtime upgrade, sandbox recovery behavior, and routing safeguards.
    • Refined the description of inference routing behavior and local Docker-driver sandbox authentication handling.
    • Adjusted the linked references and final release-note wording for consistency.

Signed-off-by: Aaron Erickson <aerickson@nvidia.com>
@ericksoa ericksoa added integration: openclaw OpenClaw integration behavior integration: hermes Hermes integration behavior area: docs Documentation, examples, guides, or docs build chore Build, CI, dependency, or tooling maintenance v0.0.88 Release target labels Jul 7, 2026
@ericksoa ericksoa self-assigned this Jul 7, 2026
@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Updated the v0.0.75 release-notes section to rephrase the OpenClaw runtime upgrade description, revise the sandbox-recovery and routing hardening bullets, update the Hermes/OpenAI routing explanation, and rewrite the local Docker-driver JWT credential bullet, along with adjusted reference links.

Changes

Release notes revision

Layer / File(s) Summary
Update v0.0.75 release notes text
docs/about/release-notes.mdx
Rephrases the OpenClaw runtime upgrade to version 2026.6.10, revises prepared-backup recovery/upgrade and route-check deferral wording, updates Hermes/OpenAI-compatible routing explanation, rewrites the Docker-driver JWT credential bullet, and updates reference links.

Estimated code review effort: 1 (Trivial) | ~3 minutes

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 accurately reflects the documentation-only update to the v0.0.75 release notes.
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 docs/fix-v0075-release-notes-accuracy

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

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • None. Docs-only release notes update; it cannot affect runtime behavior or real assistant user flows, so no E2E jobs are required.

Optional E2E

  • None.

New E2E recommendations

  • None.

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

E2E Target Recommendation

Required E2E targets: None
Optional E2E targets: None

Workflow run

Full E2E target advisor summary

E2E Target Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E targets

  • None. Docs-only release notes change; it does not affect E2E target workflow, registry, runtime support, fixtures, or live target behavior.

Optional E2E targets

  • None.

Relevant changed files

  • None.

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor (Nemotron Ultra) — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: No advisor follow-up required beyond maintainer review.
Open items: 0 required · 0 warnings · 0 suggestions · 0 test follow-ups
Since last review: 0 prior items resolved · 0 still apply · 0 new items found

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

@github-actions

github-actions Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — Changes requested

Merge posture: Do not merge yet
Primary next action: Fix PRA-1: Changed release-note bullet links to a missing manage-sandboxes page; then add or justify PRA-T1.
Open items: 1 required · 0 warnings · 0 suggestions · 2 test follow-ups
Top item: Fix the missing Set Up MCP Servers release-note link

Action checklist

  • PRA-1 Fix: Changed release-note bullet links to a missing manage-sandboxes page in docs/about/release-notes.mdx:33
  • PRA-T1 Add or justify test follow-up: Acceptance clause
  • PRA-T2 Add or justify test follow-up: Acceptance clause

Findings index

ID Severity Category Location Required action
PRA-1 Required docs docs/about/release-notes.mdx:33 Update the link to the current MCP setup page, add the missing page/redirect if this route is intended, or otherwise replace it with an existing target such as the appropriate Hermes plugin/MCP documentation page.

🚨 Required before merge

Address these before merging unless a maintainer explicitly overrides the advisor with rationale.

PRA-1 Required — Changed release-note bullet links to a missing manage-sandboxes page

  • Location: docs/about/release-notes.mdx:33
  • Category: docs
  • Problem: The updated v0.0.75 Hermes/MCP bullet sends readers to `../manage-sandboxes/set-up-mcp-servers`, but the current `docs/manage-sandboxes/` directory does not contain `set-up-mcp-servers.mdx` or an obvious same-name target.
  • Impact: Users following the release notes for managed MCP setup can hit a broken documentation route, undermining the purpose of this release-note accuracy fix.
  • Required action: Update the link to the current MCP setup page, add the missing page/redirect if this route is intended, or otherwise replace it with an existing target such as the appropriate Hermes plugin/MCP documentation page.
  • Expected follow-up: Fix before merge or get explicit maintainer override.
  • Verification: Read-only check: `ls docs/manage-sandboxes` and confirm whether `set-up-mcp-servers.mdx` exists; then inspect `docs/about/release-notes.mdx:33` to verify the link target was corrected.
  • Missing regression test: Run or extend the docs link-validation path so relative links in `docs/about/release-notes.mdx` fail when their target page is absent; specifically cover the `../manage-sandboxes/...` release-note links.
  • Done when: The required change is committed and verification passes: Read-only check: `ls docs/manage-sandboxes` and confirm whether `set-up-mcp-servers.mdx` exists; then inspect `docs/about/release-notes.mdx:33` to verify the link target was corrected.
  • Evidence: The changed line contains `[Set Up MCP Servers](../manage-sandboxes/set-up-mcp-servers)`, while the inspected directory listed `backup-restore.mdx`, `install-plugins-hermes.mdx`, `lifecycle.mdx`, `messaging-channels.mdx`, `runtime-controls.mdx`, and `workspace-files.mdx`.
Test follow-ups to resolve or justify

If these cover changed behavior, prefer adding them in this PR; otherwise state why existing coverage is enough or link the follow-up.

  • PRA-T1 Acceptance clause — Correct the v0.0.75 release-note entry merged in docs(release): add v0.0.75 release notes #6371 before the release tag is cut. — add test evidence or identify existing coverage. The diff updates only the `## v0.0.75` section in `docs/about/release-notes.mdx`, but the changed Hermes/MCP bullet still references a missing `../manage-sandboxes/set-up-mcp-servers` target.
  • PRA-T2 Acceptance clause — Tests are not applicable; `npm run docs` passed with 0 errors and 2 pre-existing warnings. — add test evidence or identify existing coverage. The PR is prose-only, and static review agrees runtime tests are not required. The claimed command result is PR-provided text and was not executed in this read-only review; the missing link above suggests docs link validation should be rechecked after the link is fixed.

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

@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.

🧹 Nitpick comments (1)
docs/about/release-notes.mdx (1)

23-24: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Use a docs route instead of the GitHub blob URL.

This should link to the release-review page through the docs router, not blob/main, so the target stays stable and matches the docs-link convention. As per coding guidelines, use route-style links without .mdx extensions for links between docs pages.

🤖 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/about/release-notes.mdx` around lines 23 - 24, The release notes link
currently points to a GitHub blob URL instead of the docs router, which makes it
inconsistent and less stable. Update the reference in the release notes to use
the docs route-style link for the OpenClaw dependency review page, following the
same internal docs-link convention used elsewhere and avoiding any .mdx
extension.

Source: Coding guidelines

🤖 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.

Nitpick comments:
In `@docs/about/release-notes.mdx`:
- Around line 23-24: The release notes link currently points to a GitHub blob
URL instead of the docs router, which makes it inconsistent and less stable.
Update the reference in the release notes to use the docs route-style link for
the OpenClaw dependency review page, following the same internal docs-link
convention used elsewhere and avoiding any .mdx extension.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 9e7ee621-0d4c-4d76-8ded-849a08a41846

📥 Commits

Reviewing files that changed from the base of the PR and between 7d50eb3 and aa9f89c.

📒 Files selected for processing (1)
  • docs/about/release-notes.mdx

@ericksoa
ericksoa merged commit bd38b38 into main Jul 7, 2026
42 checks passed
@ericksoa
ericksoa deleted the docs/fix-v0075-release-notes-accuracy branch July 7, 2026 02:15
Hadar301 pushed a commit to Hadar301/NemoClaw-OpenShift that referenced this pull request Jul 12, 2026
<!-- markdownlint-disable MD041 -->
## Summary
<!-- 1-3 sentences: what this PR does and why. -->
Correct the v0.0.75 release-note entry merged in NVIDIA#6371 before the
release tag is cut.
This follow-up restores the omitted OpenClaw `2026.6.10` upgrade and
narrows three claims to the runtime contracts that actually shipped.

## Changes
<!-- Bullet list of key changes. -->
- NVIDIA#5595 -> `docs/about/release-notes.mdx`: add the bundled OpenClaw
`2026.6.10` upgrade and its reviewed package, pairing, and recovery
boundaries.
- NVIDIA#6370 -> `docs/about/release-notes.mdx`: state that authoritative
onboarding restores the gateway provider and inference route during
rebuild, before sandbox recreation.
- NVIDIA#6335 and NVIDIA#6298 -> `docs/about/release-notes.mdx`: scope the OpenAI
frontend to Hermes while retaining the separate OpenAI-only-agent
behavior.
- NVIDIA#6304 -> `docs/about/release-notes.mdx`: name the non-expiring local
Docker-driver sandbox JWT contract precisely and link its gateway-auth
review.

## Type of Change

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

## Quality Gates
<!-- Check exactly one tests line and one docs line. Check other lines
when applicable. Add every requested justification or approval
reference. -->
- [ ] Tests added or updated for changed behavior
- [ ] Existing tests cover changed behavior — justification:
- [x] Tests not applicable — justification: prose-only release-note
corrections with no runtime behavior or code samples.
- [x] 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:

## Verification
<!-- Check each applicable item only when supported by the requested
evidence. Run targeted tests once per relevant change set and rerun
after later edits or hook autofixes that can affect the tested behavior.
Do not rerun hook-covered checks. -->
- [x] PR description includes the DCO sign-off declaration and every
commit appears as `Verified` in GitHub
- [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or
`npm run check:diff` passed when hooks were skipped or unavailable
- [x] Targeted behavior tests pass for the current change set, or tests
are marked not applicable above — command/result or justification: tests
are not applicable; `npm run docs` passed with 0 errors and 2
pre-existing warnings.
- [ ] Applicable broad gate passed — `npm test` for broad
runtime/test-harness changes; `npm run check` for repo-wide
validation/coverage changes — command/result:
- [x] Quality Gates section completed with required justifications or
waivers
- [x] No secrets, API keys, or credentials committed
- [ ] `npm run docs` builds without warnings (doc changes only) —
result: 0 errors and 2 pre-existing warnings (missing authenticated
redirects check and existing light-theme accent contrast).
- [x] Doc pages follow the [style
guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md)
(doc changes only)
- [ ] New doc pages include SPDX header and frontmatter (new pages only)

---
<!-- DCO sign-off is required in this PR description, and every commit
must appear as Verified in GitHub. Run: git config user.name && git
config user.email -->
Signed-off-by: Aaron Erickson <aerickson@nvidia.com>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Updated the `v0.0.75` release notes with clearer wording and expanded
details.
* Added more specific notes about the runtime upgrade, sandbox recovery
behavior, and routing safeguards.
* Refined the description of inference routing behavior and local
Docker-driver sandbox authentication handling.
* Adjusted the linked references and final release-note wording for
consistency.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: Aaron Erickson <aerickson@nvidia.com>
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 chore Build, CI, dependency, or tooling maintenance integration: hermes Hermes integration behavior integration: openclaw OpenClaw integration behavior v0.0.88 Release target

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants