chore: prepare 0.7 code freeze - #601
Conversation
Signed-off-by: Will Killian <wkillian@nvidia.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📜 Recent review details⏰ Context from checks skipped due to timeout. (1)
🧰 Additional context used📓 Path-based instructions (8)**/*.mdx📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)
Files:
**/*.{md,mdx}📄 CodeRabbit inference engine (AGENTS.md)
Files:
**/*.{md,markdown,mdx}📄 CodeRabbit inference engine (CONTRIBUTING.md)
Files:
{docs,examples}/**/*📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)
Files:
**/*📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)
Files:
docs/**/*📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)
Files:
**/*.{md,mdx,py,go,js,ts}📄 CodeRabbit inference engine (.agents/skills/maintain-observability/SKILL.md)
Files:
{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}⚙️ CodeRabbit configuration file
Files:
🧠 Learnings (1)📓 Common learnings🔇 Additional comments (1)
WalkthroughThe release version changes from 0.7.0 to 0.8.0 across workspace metadata, package manifests, integrations, documentation, and release tooling. The code-freeze workflow now regenerates and validates the worker-plugin fixture lockfile. ChangesRelease version alignment
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
github-actions
Bot
added
size:M
License DiffCompared against Lockfile license changesLockfile License ChangesRustAdded
Removed
Updated/Changed
NodeAdded
Removed
Updated/Changed
PythonAdded
Removed
Updated/Changed
Status output |
Signed-off-by: Will Killian <wkillian@nvidia.com>
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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 @.agents/skills/prepare-code-freeze/SKILL.md:
- Around line 46-48: Insert a blank line after the closing fenced command block
in SKILL.md, before step 7, so the Markdown satisfies MD031.
- Around line 65-66: Reorder the worker_plugin validation commands so `cargo
build --locked --manifest-path
crates/core/tests/fixtures/worker_plugin/Cargo.toml` runs before `cargo
generate-lockfile`; then verify regeneration causes no committed changes with
`git diff --exit-code -- crates/core/tests/fixtures/worker_plugin/Cargo.lock`.
In `@docs/getting-started/quick-start/python.mdx`:
- Line 23: Update the uv add command in the quick-start example to use the
exact-version requirement syntax with == instead of @, while keeping the
nemo-relay package and version unchanged.
🪄 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: ASSERTIVE
Plan: Enterprise
Run ID: 82a941f6-c7a9-4312-ada6-581e9acce689
⛔ Files ignored due to path filters (4)
Cargo.lockis excluded by!**/*.lockcrates/core/tests/fixtures/worker_plugin/Cargo.lockis excluded by!**/*.lockpackage-lock.jsonis excluded by!**/package-lock.jsonuv.lockis excluded by!**/*.lock
📒 Files selected for processing (18)
.agents/skills/prepare-code-freeze/SKILL.md.github/nightly-alpha-branches.yamlCargo.tomlREADME.mdcrates/node/package.jsondocs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdxdocs/getting-started/installation.mdxdocs/getting-started/quick-start/nodejs.mdxdocs/getting-started/quick-start/python.mdxdocs/getting-started/quick-start/rust.mdxdocs/supported-integrations/openclaw-plugin.mdxintegrations/coding-agents/claude-code/.claude-plugin/plugin.jsonintegrations/coding-agents/codex/.codex-plugin/plugin.jsonintegrations/openclaw/package.jsonpackages/cli-bin/package.jsonpyproject.tomlpython/cli-bin/pyproject.tomlpython/plugin/pyproject.toml
📜 Review details
⏰ Context from checks skipped due to timeout. (10)
- GitHub Check: Rust / Test (linux-arm64)
- GitHub Check: Python / Test (macos-arm64)
- GitHub Check: Python / Test (windows-amd64)
- GitHub Check: Rust / Test (macos-arm64)
- GitHub Check: Rust / Test (windows-arm64)
- GitHub Check: Python / Test (windows-arm64)
- GitHub Check: Node.js / Test (windows-arm64)
- GitHub Check: Rust / Test (windows-amd64)
- GitHub Check: Rust / Test (linux-amd64)
- GitHub Check: Node.js / Test (windows-amd64)
🧰 Additional context used
📓 Path-based instructions (32)
.github/nightly-alpha-branches.yaml
📄 CodeRabbit inference engine (.agents/skills/prepare-code-freeze/SKILL.md)
Update
.github/nightly-alpha-branches.yamlto include the new release branch.
Files:
.github/nightly-alpha-branches.yaml
.github/{nightly-alpha-branches.yaml,workflows/nightly-alpha-tag.yaml}
📄 CodeRabbit inference engine (.agents/skills/prepare-code-freeze/SKILL.md)
Validate the nightly alpha branch and workflow YAML files by loading them with Ruby's YAML parser.
Files:
.github/nightly-alpha-branches.yaml
{.github/**,.gitlab-ci.yml,.pre-commit-config.yaml,justfile,scripts/**}
⚙️ CodeRabbit configuration file
{.github/**,.gitlab-ci.yml,.pre-commit-config.yaml,justfile,scripts/**}: Review automation changes for reproducibility, pinned versions where appropriate, secret handling, and consistency with the documented validation matrix.
Pay attention to commands that need generated native artifacts, FFI libraries, or platform-specific environment variables.
Files:
.github/nightly-alpha-branches.yaml
crates/node/**/*.{js,ts,jsx,tsx,json}
📄 CodeRabbit inference engine (.agents/skills/test-node-binding/SKILL.md)
Format changed Node files with
npm run format --workspace=nemo-relay-node
Files:
crates/node/package.json
crates/node/package.json
📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)
Keep the Node package metadata in
crates/node/package.jsonconsistent with the package name, versioning, and publish surface.Keep the
crates/node/package.jsonpackage version aligned with the workspace-rootpackage-lock.json, and keep itsdependencies["nemo-relay-node"]entry aligned when the Node package version changes.
Files:
crates/node/package.json
**/*
📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)
**/*: Format changed files with the language-native formatter before the final lint/test pass.
If dynamic plugin behavior changed, usemaintain-dynamic-pluginsand include the native SDK, worker protocol, Python SDK, docs, packaging, and Codecov surfaces in the validation plan.
If code changes alter APIs, bindings, commands, paths, packaging behavior, observability/adaptive semantics, or documented best practices, update any dependent maintainer or consumer skills in the same branch.
During iteration, preferuv run pre-commit run --files <changed files...>.
Before review or handoff, runuv run pre-commit run --all-files.
Files:
crates/node/package.jsondocs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdxpyproject.tomlCargo.tomlpython/plugin/pyproject.tomldocs/getting-started/quick-start/python.mdxpython/cli-bin/pyproject.tomldocs/supported-integrations/openclaw-plugin.mdxintegrations/openclaw/package.jsonREADME.mdpackages/cli-bin/package.jsondocs/getting-started/quick-start/rust.mdxdocs/getting-started/quick-start/nodejs.mdxdocs/getting-started/installation.mdx
crates/{python,ffi,node}/**/*
⚙️ CodeRabbit configuration file
crates/{python,ffi,node}/**/*: Treat binding changes as public API changes. Check for parity with the other language bindings, FFI ownership/lifetime safety,
callback error propagation, stable type conversion, and consistent async/stream semantics.
Flag changes that update one binding without corresponding tests or documentation for the same surface elsewhere.
Files:
crates/node/package.json
**/*.mdx
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)
MDX top-of-file SPDX comments must use {/* ... */} delimiters instead of HTML comment delimiters (Must-Fix)
In MDX files, top-of-file comments must use JSX comment delimiters (
{/*to open and*/}to close); do not use HTML comments for MDX SPDX headers
Files:
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdxdocs/getting-started/quick-start/python.mdxdocs/supported-integrations/openclaw-plugin.mdxdocs/getting-started/quick-start/rust.mdxdocs/getting-started/quick-start/nodejs.mdxdocs/getting-started/installation.mdx
**/*.{md,mdx}
📄 CodeRabbit inference engine (AGENTS.md)
Update
README.md,fern/, package READMEs, and binding-support notes when public behavior, package names, examples, or supported bindings change.
**/*.{md,mdx}: Prefer the documented public API, not internal shortcuts
Keep package names, repo references, and build commands current
Keep release-process and release-notes guidance in repo-maintainer docs such asRELEASING.md, not as user-facing docs pages orCHANGELOG.md
Keep stable user-facing wrappers atscripts/root in docs and examples; only point at namespaced helper paths when documenting internal maintenance work
When detailed dynamic plugin guides exist, keep Rust native plugin examples, Python worker plugin examples, andgrpc-v1protocol details on separate pagesIf links in documentation change, run
just docs-linkcheck.
Files:
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdxdocs/getting-started/quick-start/python.mdxdocs/supported-integrations/openclaw-plugin.mdxREADME.mddocs/getting-started/quick-start/rust.mdxdocs/getting-started/quick-start/nodejs.mdxdocs/getting-started/installation.mdx
**/*.{md,markdown,mdx}
📄 CodeRabbit inference engine (CONTRIBUTING.md)
Add the SPDX license header to all Markdown/MDX documentation files using the HTML comment block form.
Files:
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdxdocs/getting-started/quick-start/python.mdxdocs/supported-integrations/openclaw-plugin.mdxREADME.mddocs/getting-started/quick-start/rust.mdxdocs/getting-started/quick-start/nodejs.mdxdocs/getting-started/installation.mdx
{crates/core/src/plugin/dynamic/**,crates/plugin/**,crates/worker/**,crates/worker-proto/**,crates/types/**,python/plugin/**,examples/rust-native-plugin/**,examples/python-grpc-worker-plugin/**,docs/build-plugins/**}
📄 CodeRabbit inference engine (.agents/skills/maintain-dynamic-plugins/SKILL.md)
Keep the stable boundary explicit: native plugins cross a C ABI, and worker plugins cross
grpc-v1.
Files:
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdxpython/plugin/pyproject.toml
{crates/core/src/plugin/dynamic/**,examples/rust-native-plugin/**,examples/python-grpc-worker-plugin/**,docs/build-plugins/**}
📄 CodeRabbit inference engine (.agents/skills/maintain-dynamic-plugins/SKILL.md)
Native and worker plugins are trusted extensions; document that native plugins are in-process and unsandboxed, and worker plugins provide process isolation but not a security sandbox.
Files:
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdx
{docs/build-plugins/**,examples/rust-native-plugin/**,examples/python-grpc-worker-plugin/**}
📄 CodeRabbit inference engine (.agents/skills/maintain-dynamic-plugins/SKILL.md)
When detailed dynamic plugin guides exist, keep Rust native, Python worker, and
grpc-v1protocol details on separate pages.
Files:
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdx
{docs,examples}/**/*
📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)
Update docs and examples.
Files:
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdxdocs/getting-started/quick-start/python.mdxdocs/supported-integrations/openclaw-plugin.mdxdocs/getting-started/quick-start/rust.mdxdocs/getting-started/quick-start/nodejs.mdxdocs/getting-started/installation.mdx
docs/**/*
📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)
If documentation examples or commands under
docs/change, run the targeted docs checks appropriate to the change.
Files:
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdxdocs/getting-started/quick-start/python.mdxdocs/supported-integrations/openclaw-plugin.mdxdocs/getting-started/quick-start/rust.mdxdocs/getting-started/quick-start/nodejs.mdxdocs/getting-started/installation.mdx
**/*.{md,mdx,py,go,js,ts}
📄 CodeRabbit inference engine (.agents/skills/maintain-observability/SKILL.md)
Examples and documentation must use each exporter's documented flush/deregister order before shutdown.
Files:
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdxdocs/getting-started/quick-start/python.mdxdocs/supported-integrations/openclaw-plugin.mdxREADME.mddocs/getting-started/quick-start/rust.mdxdocs/getting-started/quick-start/nodejs.mdxdocs/getting-started/installation.mdx
{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}
⚙️ CodeRabbit configuration file
{docs/**,README.md,CONTRIBUTING.md,RELEASING.md,SECURITY.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency across language bindings.
Flag stale examples, missing SPDX headers where required, and instructions that no longer match CI or pre-commit behavior.
Files:
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdxdocs/getting-started/quick-start/python.mdxdocs/supported-integrations/openclaw-plugin.mdxREADME.mddocs/getting-started/quick-start/rust.mdxdocs/getting-started/quick-start/nodejs.mdxdocs/getting-started/installation.mdx
**/*.toml
📄 CodeRabbit inference engine (CONTRIBUTING.md)
Add the SPDX license header to all TOML files using the
#comment form.
Files:
pyproject.tomlCargo.tomlpython/plugin/pyproject.tomlpython/cli-bin/pyproject.toml
pyproject.toml
📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)
Keep Python packaging metadata in the root
pyproject.tomlconsistent with the package’s published name, imports, and build behavior.
Files:
pyproject.toml
**/Cargo.toml
📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)
Keep Rust package names and workspace metadata in
Cargo.tomlinternally consistent across the project.OpenTelemetry and OpenInference dependencies must be unconditional rather than Cargo feature-gated.
Files:
Cargo.toml
Cargo.toml
📄 CodeRabbit inference engine (.agents/skills/update-project-version/SKILL.md)
In
Cargo.toml, treat[workspace.package].versionas the source of truth for the Rust workspace and Python build versioning, and keepworkspace.dependencies.nemo-relay.version,workspace.dependencies.nemo-relay-adaptive.version,workspace.dependencies.nemo-relay-pii-redaction.version,workspace.dependencies.nemo-relay-ffi.version, andworkspace.dependencies.nemo-relay-cli.versionaligned when the workspace version changes.
Cargo.toml: Confirm or infer the target release version fromupstream/main:Cargo.tomland derive the release branch asrelease/<major>.<minor>.
Runjust set-version <next-version>to update all release-versioned package surfaces onmain.
Files:
Cargo.toml
python/plugin/pyproject.toml
📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)
Keep the Python worker plugin SDK packaging metadata in
python/plugin/pyproject.tomlaligned with the project’s release and import paths.
Files:
python/plugin/pyproject.toml
integrations/openclaw/package.json
📄 CodeRabbit inference engine (.agents/skills/update-project-version/SKILL.md)
Keep the
integrations/openclaw/package.jsonpackage version aligned with the workspace-rootpackage-lock.json, and keep itsdependencies["nemo-relay-node"]entry aligned when the OpenClaw package version changes.
Files:
integrations/openclaw/package.json
**/*.{md,rst,html,txt}
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)
**/*.{md,rst,html,txt}: Always spellNVIDIAin all caps. Do not useNvidia,nvidia,nVidia,nVIDIA, orNV.
Usean NVIDIAbefore a noun because the name starts with an 'en' sound.
Do not add a registered trademark symbol afterNVIDIAwhen referring to the company.
Use trademark symbols with product names only when the document type or legal guidance requires them.
Verify official capitalization, spacing, and hyphenation for product names.
Precede NVIDIA product names withNVIDIAon first mention when it is natural and accurate.
Do not rewrite product names for grammar or title-case rules.
Preserve third-party product names according to the owner's spelling.
Include the company name and full model qualifier on first use when it helps identify the model.
Preserve the official capitalization and punctuation of model names.
Use shorter family names only after the full name is established.
Spell out a term on first use and put the acronym in parentheses unless the acronym is widely understood by the intended audience.
Use the acronym on later mentions after it has been defined.
For long documents, reintroduce the full term if readers might lose context.
Form plurals of acronyms withs, not an apostrophe, such asGPUs.
In headings, common acronyms can remain abbreviated. Spell out the term in the first or second sentence of the body.
Common terms such asCPU,GPU,PC,API, andUIusually do not need to be spelled out for developer audiences.
Files:
README.md
**/*.{md,rst,html}
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-brand-terminology.md)
Link the first mention of a product name when the destination helps the reader.
Files:
README.md
**/*.{md,rst,txt}
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)
Spell
NVIDIAin all caps. Do not useNvidia,nvidia, orNV.
Files:
README.md
**/*.{md,rst}
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)
**/*.{md,rst}: Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text. Avoid raw URLs and weak anchors such as "here" or "read more."
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative steps. Keep steps parallel and split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English.
Usecanfor possibility and reservemayfor permission.
Useafterfor temporal relationships instead ofonce.
Preferrefer tooverseewhen the wording points readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical docs.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values.
Use numerals for 10 or greater and include commas in thousands.
Do not add trademark symbols to learning-oriented docs unless the source, platform, or legal guidance explicitly requires them.
Files:
README.md
**/*.md
📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-technical-docs.md)
**/*.md: Use title case consistently in technical documentation headings
Avoid quotation marks, ampersands, and exclamation marks in headings
Keep product, event, research, and whitepaper names in their official title case
Use title case for table headers
Do not force social-media sentence case into technical docs
Format code elements, commands, parameters, package names, and expressions in monospace
Format directories, file names, and paths in monospace using backticks
Use angle brackets inside monospace for variables inside paths, such as/home/<username>/.login
Format error messages and strings in quotation marks, keeping literal code strings in code formatting when clearer
Format UI buttons, menus, fields, and labels in bold
Use angle brackets between UI labels for menu paths, such as File > Save As
Use italics for new terms on first use, sparingly and only when introducing the term
Use italics for publication titles
Format keyboard shortcuts in plain text, such as Press Ctrl+Alt+Delete
Use owner/repo link text for GitHub repositories, preferring[NVIDIA/NeMo](link)over prose references like 'the GitHub repo'
Introduce every code block with a complete sentence
Do not make a code block complete the grammar of the previous sentence
Do not continue a sentence after a code block
Use syntax highlighting when the format supports it for code blocks
Avoid the word 'snippet' unless the surrounding docs already use it as a term of art
Keep inline method, function, and class references consistent with nearby docs, omitting empty parentheses for prose readability when no call is shown
Use descriptive anchor text that matches the destination title when possible for links
Avoid raw URLs in running text
Avoid generic anchor text such as 'here,' 'this page,' and 'read more'
Include acronyms in link text when a linked term includes an acronym
Do not link long sentences or multiple sentences
Avoid links that pull readers away from a procedure unless the link is a p...
Files:
README.md
{docs/**/*.md,README.md}
📄 CodeRabbit inference engine (.agents/skills/add-binding-feature/SKILL.md)
Update reference docs, language-binding docs, READMEs, and example documentation when the public surface or expected usage changes.
Files:
README.md
{README.md,docs/index.md}
📄 CodeRabbit inference engine (.agents/skills/contribute-docs/SKILL.md)
Update entry-point docs when examples or reading paths change
Files:
README.md
README.md
📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)
If documentation examples or commands in
README.mdchange, run the targeted docs checks appropriate to the change.
Files:
README.md
{README.md,docs/**/*.md,fern/**/*}
📄 CodeRabbit inference engine (.agents/skills/prepare-code-freeze/SKILL.md)
{README.md,docs/**/*.md,fern/**/*}: Update current-version documentation install commands, package examples, and configuration examples from the old version to<next-version>where appropriate.
Leave intentional historical version references unchanged, including release notes, changelogs, generated build output, and third-party dependency attribution entries.
Files:
README.md
🧠 Learnings (1)
📓 Common learnings
Learnt from: CR
Repo: NVIDIA/NeMo-Relay
Timestamp: 2026-07-31T15:47:49.685Z
Learning: Prompt for `<next-version>` when it is not provided; this is the version that `main` adopts after the release branch is created.
Learnt from: CR
Repo: NVIDIA/NeMo-Relay
Timestamp: 2026-07-31T15:47:49.685Z
Learning: Create the release branch from the latest `upstream/main` and push it to the upstream repository; if it already exists, verify that it points to the expected commit.
Learnt from: CR
Repo: NVIDIA/NeMo-Relay
Timestamp: 2026-07-31T15:47:49.685Z
Learning: Create the code-freeze PR branch from the latest `upstream/main`.
Learnt from: CR
Repo: NVIDIA/NeMo-Relay
Timestamp: 2026-07-31T15:47:49.685Z
Learning: Run `git diff --check` and ensure validation passes before opening the PR.
Learnt from: CR
Repo: NVIDIA/NeMo-Relay
Timestamp: 2026-07-31T15:47:49.685Z
Learning: The PR description must mention the new release branch, nightly alpha configuration update, version bump, documentation updates or intentional leftovers, and that release-bound PRs now target the new `release/*` branch.
Learnt from: CR
Repo: NVIDIA/NeMo-Relay
Timestamp: 2026-07-31T15:47:49.685Z
Learning: Do not create release tags; code freeze creates only the release branch and the main PR.
Learnt from: CR
Repo: NVIDIA/NeMo-Relay
Timestamp: 2026-07-31T15:47:49.685Z
Learning: Do not target the code-freeze PR at the release branch; target `main`.
Learnt from: CR
Repo: NVIDIA/NeMo-Relay
Timestamp: 2026-07-31T15:47:49.685Z
Learning: Do not leave uncommitted user changes mixed into the code-freeze PR branch.
🪛 markdownlint-cli2 (0.23.1)
.agents/skills/prepare-code-freeze/SKILL.md
[warning] 48-48: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
🔇 Additional comments (15)
Cargo.toml (1)
24-40: LGTM!packages/cli-bin/package.json (1)
3-3: LGTM!pyproject.toml (1)
70-70: 🗄️ Data Integrity & IntegrationVerify the local CLI package version before merging.
Line 70 pins
nemo-relay-cli-binto0.8.0, while[tool.uv.sources]resolves that package frompython/cli-bin. Confirm thatpython/cli-bin/pyproject.tomldeclares0.8.0and refresh or validate the uv lockfile.As per path instructions,
pyproject.tomlmust keep Python packaging metadata consistent with the package's published name and build behavior.Source: Path instructions
docs/getting-started/quick-start/nodejs.mdx (1)
22-22: LGTM!docs/getting-started/quick-start/rust.mdx (1)
21-21: LGTM!Also applies to: 30-30, 50-51
docs/supported-integrations/openclaw-plugin.mdx (1)
45-45: LGTM!Also applies to: 58-58
crates/node/package.json (1)
3-3: 🗄️ Data Integrity & IntegrationNo metadata mismatch remains. The package manifests and
package-lock.jsonuse0.8.0consistently.python/cli-bin/pyproject.toml (1)
10-10: LGTM!python/plugin/pyproject.toml (1)
11-11: LGTM!integrations/coding-agents/claude-code/.claude-plugin/plugin.json (1)
3-3: LGTM!integrations/coding-agents/codex/.codex-plugin/plugin.json (1)
3-3: LGTM!.github/nightly-alpha-branches.yaml (1)
4-6: 📐 Maintainability & Code QualityValidate the updated YAML configuration.
As per path instructions, load
.github/nightly-alpha-branches.yamland.github/workflows/nightly-alpha-tag.yamlwith Ruby's YAML parser before handoff.Source: Path instructions
README.md (1)
235-235: 📐 Maintainability & Code QualityRun the targeted README checks.
This change updates a user-facing installation command. As per path instructions, run the targeted documentation checks appropriate to the
README.mdchange before handoff.Source: Path instructions
docs/build-plugins/dynamic-plugins/native-dynamic/rust-native-plugin-example.mdx (1)
32-32: 📐 Maintainability & Code QualityRun the targeted documentation checks.
This change updates a Cargo dependency in a documentation example. As per path instructions, run the targeted checks appropriate to changes under
docs/.Source: Path instructions
docs/getting-started/installation.mdx (1)
126-126: 📐 Maintainability & Code QualityRun the targeted documentation checks.
These changes update installation commands under
docs/. As per path instructions, run the targeted checks appropriate to the changed documentation examples.Also applies to: 150-150, 204-204, 219-228, 245-245, 283-283
Source: Path instructions
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Signed-off-by: Will Killian <2007799+willkill07@users.noreply.github.com>
|
/merge |
2 participants
Overview
Prepare
mainfor the NeMo Relay 0.7 code freeze and post-freeze development on 0.8.0.Details
release/0.7to the nightly alpha branch configuration. Release-bound PRs should now target that branch.just set-version 0.8.0to advance Cargo, Python, Node, CLI, OpenClaw, and coding-agent package surfaces onmain.Where should the reviewer start?
Start with
.github/nightly-alpha-branches.yamlandCargo.toml; the remainder is the synchronized 0.8.0 version and documentation update.Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)
Summary by CodeRabbit
Release
Documentation
Validation