Skip to content

docs(changelog): add v0.0.110 release entry - #9380

Merged
ericksoa merged 1 commit into
mainfrom
codex/release-docs-v0.0.110
Aug 18, 2026
Merged

ericksoa merged 1 commit into
mainfrom
codex/release-docs-v0.0.110

Conversation

@cjagwani

@cjagwani cjagwani commented Aug 18, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Add the canonical dated changelog entry required before planning the v0.0.110 release. The entry summarizes user-facing changes merged since v0.0.109 and links each change to its published documentation route and source PR.

Changes

  • Add docs/changelog/2026-08-17.mdx with the exact ## v0.0.110 release heading.
  • Cover managed local inference, endpoint validation, onboarding and recovery, explicit experimental Portable OpenClaw, messaging and policy cleanup, backup and security hardening, and release qualification.
  • Preserve the documentation skip list and the current supported-agent matrix; test-only refactors, dormant activation work, and Pi-only changes are intentionally excluded.

Source-to-doc mapping

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: test/changelog-docs.test.ts validates the dated release-entry contract.
  • Tests 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:

DGX Station Hardware Evidence

  • Tested on DGX Station
  • Tested commit: Not applicable; documentation-only change.
  • 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 — npx vitest run test/changelog-docs.test.ts (7 passed)
  • 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 one prose-only changelog page; npm run docs passed the repository's strict documentation gate.
  • 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) — passed with 0 errors and the 2 existing Fern warnings.
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only) — the SPDX header is present; dated changelog pages intentionally do not use frontmatter.

Signed-off-by: Charan Jagwani cjagwani@nvidia.com

Summary by CodeRabbit

  • Documentation
    • Added release notes for v0.0.110.
    • Documented experimental managed llama.cpp and Portable OpenClaw profiles.
    • Covered inference validation, onboarding and recovery improvements, rootless lifecycle handling, messaging and policy updates, backups, credential handling, filesystem protections, and release qualification updates.

@cjagwani cjagwani added area: docs Documentation, examples, guides, or docs build v0.0.110 labels Aug 18, 2026
@cjagwani cjagwani self-assigned this Aug 18, 2026
@coderabbitai

coderabbitai Bot commented Aug 18, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 6f721b44-9790-4f09-b583-0e9827ce7d34

📥 Commits

Reviewing files that changed from the base of the PR and between c2a7292 and e15a313.

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

Included review availability: Your plan includes up to 12 reviews per rolling hour; 11 remain after this review.


📝 Walkthrough

Walkthrough

The v0.0.110 changelog documents runtime profiles, endpoint validation, lifecycle handling, safety controls, messaging updates, credential management, and release qualification requirements.

Changes

Release changelog

Layer / File(s) Summary
Runtime profiles and validation
docs/changelog/2026-08-17.mdx
Documents managed llama.cpp and vLLM profiles, endpoint validation, diagnostics, tool-use requirements, and Model Router lifecycle operations.
Sandbox and Portable lifecycle
docs/changelog/2026-08-17.mdx
Documents sandbox readiness and recovery, rootless Podman lifecycle handling, receipt-bound cleanup, filesystem protections, and startup diagnostics.
Messaging and release qualification
docs/changelog/2026-08-17.mdx
Documents messaging cleanup, package and credential validation, Google Chat recovery, release qualification, retry rules, and documentation workflow requirements.

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

Merge Risk: ⚪ Minimal · up to e15a3

This change adds the v0.0.110 release documentation entry without modifying product behavior, so no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: aasthajh, afourniernv, ahunnargikar-nvidia

🚥 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.110 changelog release 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/release-docs-v0.0.110

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

@github-actions

Copy link
Copy Markdown
Contributor

@ericksoa ericksoa left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Reviewed commit e15a313. The dated v0.0.110 entry follows the release-documentation contract, and required checks pass.

@ericksoa
ericksoa merged commit d466b1b into main Aug 18, 2026
59 of 60 checks passed
@ericksoa
ericksoa deleted the codex/release-docs-v0.0.110 branch August 18, 2026 02:00
@github-actions

github-actions Bot commented Aug 18, 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): Failed

Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests.

5 semantic terminology decisions

Terminology decisions are advisory. They affect the assessment only when a separate finding identifies concrete semantic impact.

  • established — Portable OpenClaw at docs/changelog/2026-08-17.mdx:9: Keep `Portable OpenClaw` for this established profile.
  • established — receipt-bound at docs/changelog/2026-08-17.mdx:9: Keep `receipt-bound` for operations limited to receipt-owned resources.
  • define — native tool-use evidence at docs/changelog/2026-08-17.mdx:8: Define this term where it is reused, with the required native block and stop-reason criteria.
  • define — probe-only convergence at docs/changelog/2026-08-17.mdx:28: Define this term outside the release entry if it becomes a reusable recovery term.
  • justified — credential-free native-runtime qualification matrix at docs/changelog/2026-08-17.mdx:53: Keep `credential-free` because it states the relevant credential boundary.

E2E guidance

Advisory only. A maintainer can dispatch the default E2E suite for the commit under review.

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.

@wscurran wscurran added the chore Build, CI, dependency, or tooling maintenance label Oct 29, 2026
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants