chore: prepare 0.2 code freeze by AnuradhaKaruppiah · Pull Request #239 · NVIDIA/NeMo-Fabric

AnuradhaKaruppiah · 2026-08-15T01:09:51Z

Overview

Create the NVIDIA NeMo Fabric 0.2 release line and advance main to the next development version.

The release/0.2 branch was created from upstream/main at f8ca05e12eca5973a2ee24aa4ba83099c82e617b. Release-bound pull requests should now target release/0.2; work intended for later releases should continue to target main.

Nightly alpha tagging remains on main. No CI branch configuration change is needed, so nightly tags will use the new 0.3.0 development version after this PR merges.

Details

Ran just set-version 0.3.0 to synchronize Cargo, Python, TypeScript, internal dependency pins, and lockfiles.
Updated current README, Harbor, SWE-bench, and notebook package-version examples from 0.2.0 to 0.3.0.
Preserved the dynamically derived nemo-fabric-runtime version.
Confirmed that no current-version 0.2.0 references remain in README.md, docs/, examples/, or adapters/, excluding generated API references.

Validation

cargo check --workspace --locked
PYO3_PYTHON=.venv/bin/python just build-all
PYO3_PYTHON=.venv/bin/python just wheels
just --fmt --check
just pack-typescript with Node 22.22.2
jq empty examples/notebooks/01_quickstart.ipynb examples/notebooks/02_variations.ipynb
git diff --check

Where should the reviewer start?

Start with Cargo.toml for the canonical version bump, then review sdk/python/nemo-fabric/pyproject.toml and the current-version examples in README.md.

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

Relates to: none
I confirm this contribution is my own work, or I have the right to submit it under this project's license.
I searched existing issues and open pull requests, and this does not duplicate existing work.

Summary by CodeRabbit

Release
- Updated the NeMo Fabric ecosystem to version 0.3.0, including the core package, runtime, SDK, adapter contracts, and supported adapters.
- Updated package requirements and installation examples to use the new release consistently.
Documentation
- Refreshed quickstart notebooks, Harbor guides, and installation instructions for version 0.3.0.

Signed-off-by: Anuradha Karuppiah <26330987+AnuradhaKaruppiah@users.noreply.github.com>

coderabbitai · 2026-08-15T01:10:15Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 93fbb4f6-3d15-4c30-8a6f-e33853ceafae

📥 Commits

Reviewing files that changed from the base of the PR and between f8ca05e and 86729bb.

⛔ Files ignored due to path filters (11)

Cargo.lock is excluded by !**/*.lock
adapter-contract/python/uv.lock is excluded by !**/*.lock
adapter-contract/typescript/package-lock.json is excluded by !**/package-lock.json
adapters/claude/uv.lock is excluded by !**/*.lock
adapters/codex/uv.lock is excluded by !**/*.lock
adapters/common/uv.lock is excluded by !**/*.lock
adapters/deepagents/uv.lock is excluded by !**/*.lock
adapters/hermes/uv.lock is excluded by !**/*.lock
adapters/mini-swe-agent/uv.lock is excluded by !**/*.lock
sdk/python/nemo-fabric/uv.lock is excluded by !**/*.lock
uv.lock is excluded by !**/*.lock

📒 Files selected for processing (16)

Cargo.toml
README.md
adapter-contract/python/pyproject.toml
adapter-contract/typescript/package.json
adapters/claude/pyproject.toml
adapters/codex/pyproject.toml
adapters/common/pyproject.toml
adapters/deepagents/pyproject.toml
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
examples/harbor/README.md
examples/harbor/swebench/README.md
examples/notebooks/01_quickstart.ipynb
examples/notebooks/02_variations.ipynb
pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

📜 Recent review details

⏰ Context from checks skipped due to timeout. (20)

GitHub Check: Preview docs
GitHub Check: Test (Python 3.13, windows-amd64)
GitHub Check: Test (Python 3.14, windows-amd64)
GitHub Check: Test (Python 3.11, windows-amd64)
GitHub Check: Test (Python 3.14, macos-arm64)
GitHub Check: Test (Python 3.13, linux-amd64)
GitHub Check: Test (Python 3.12, windows-amd64)
GitHub Check: Test (Python 3.14, linux-amd64)
GitHub Check: Test (Python 3.14, linux-arm64)
GitHub Check: Test (Python 3.13, macos-arm64)
GitHub Check: Test (Python 3.11, linux-amd64)
GitHub Check: Test (Python 3.11, linux-arm64)
GitHub Check: Test (Python 3.12, macos-arm64)
GitHub Check: Test (Python 3.12, linux-arm64)
GitHub Check: Test (Python 3.11, macos-arm64)
GitHub Check: Test (Python 3.12, linux-amd64)
GitHub Check: Test (Python 3.13, linux-arm64)
GitHub Check: Pre-commit
GitHub Check: Test (arm64)
GitHub Check: Test (x86_64)

🧰 Additional context used

📓 Path-based instructions (32)

**/*

📄 CodeRabbit inference engine (.agents/skills/karpathy-guidelines/SKILL.md)

**/*: Before implementing, explicitly state assumptions, surface ambiguity and tradeoffs, present multiple interpretations when relevant, and ask for clarification rather than silently deciding or proceeding when requirements are unclear.
Prefer the minimum code needed to solve the requested problem: avoid speculative features, unnecessary abstractions, unrequested flexibility, and handling of impossible scenarios; simplify overcomplicated solutions.
When editing existing code, make surgical changes only: do not modify unrelated code, comments, formatting, or pre-existing dead code; match the existing style, and remove only unused imports, variables, or functions introduced by your changes.
Define verifiable success criteria for each task, such as writing regression tests for bugs and invalid-input tests for validation, then verify the implementation against those criteria. For multi-step work, state a brief plan with a verification check for each step.

**/*: Always spell NVIDIA in all caps; do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun, because the name begins with an “en” sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company; use trademark symbols with product names only when required by the document type or legal guidance.
Verify official capitalization, spacing, hyphenation, and spelling for NVIDIA and third-party product names; do not rewrite official product names for grammar or title-case rules.
Precede NVIDIA product names with NVIDIA on first mention when natural and accurate, and link the first mention when the destination helps the reader.
On first use, include the company name and full model qualifier when it helps identify the model; preserve official capitalization and punctuation, and use shorter family names only after establishing the full name.
For learning-oriented and developer content, do not force trademark symbols unless explicitly required; for press, ...

Files:

adapter-contract/python/pyproject.toml
adapter-contract/typescript/package.json
examples/harbor/swebench/README.md
pyproject.toml
examples/notebooks/02_variations.ipynb
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
examples/harbor/README.md
examples/notebooks/01_quickstart.ipynb
README.md
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
Cargo.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

**/*.{rs,toml}

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

For any Rust change, run just test-rust and cargo fmt --all -- --check.

**/*.{rs,toml}: - Rust core, CLI, or shared runtime semantics changed
Run Rust formatting and tests. Add Python tests when the behavior is exposed through the SDK, and run relevant tests for CLI behavior.

Files:

adapter-contract/python/pyproject.toml
pyproject.toml
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
Cargo.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

**/{Cargo.toml,Cargo.lock,pyproject.toml,package.json}

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

For new or updated dependencies, document the functional need, alternatives considered, and why the selected dependency is the narrowest fit.

Files:

adapter-contract/python/pyproject.toml
adapter-contract/typescript/package.json
pyproject.toml
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
Cargo.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

{docs/sdk/python.mdx,schemas/SCHEMA.md,docs/reference/api/**/*,skills/**/*,adapter-contract/**/*,typescript/adapter-contract/**/*}

📄 CodeRabbit inference engine (AGENTS.md)

{docs/sdk/python.mdx,schemas/SCHEMA.md,docs/reference/api/**/*,skills/**/*,adapter-contract/**/*,typescript/adapter-contract/**/*}: - Keep public bindings current when the API changes: docs/sdk/python.mdx for
the Python SDK; adapter-contract/ and typescript/adapter-contract/ for the
southbound adapter contract; the JSON Schema notes in schemas/SCHEMA.md;
the generated references under docs/reference/api/; and the integration
skills under skills/ (which restate public contracts and must be kept in
parity). Regenerate docs with just docs after changing the docs site.

Files:

adapter-contract/python/pyproject.toml
adapter-contract/typescript/package.json

**/pyproject.toml

📄 CodeRabbit inference engine (.agents/skills/update-project-version/SKILL.md)

Run just build-python to verify all Python package metadata resolves.

**/pyproject.toml: Keep nemo-fabric as a metapackage that unconditionally installs the
exact-version nemo-fabric-runtime distribution.
Keep leaf adapters adapter-only by default.
First prefer the standard library, an existing dependency, or a small local
implementation when it keeps the behavior clear and maintainable.
When multiple dependencies satisfy the technical requirement, prefer the
maintained OSS option with clear SPDX metadata, a smaller transitive graph,
and permissive terms such as Apache-2.0, MIT, BSD, or ISC.

The editable maturin build still produces nemo_fabric._native

Files:

adapter-contract/python/pyproject.toml
pyproject.toml
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

**/{Cargo.toml,Cargo.lock,pyproject.toml,uv.lock}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

**/{Cargo.toml,Cargo.lock,pyproject.toml,uv.lock}: - If a Cargo or Python manifest or lockfile changed, run
uv run --no-project python scripts/licensing/license_diff.py --base-ref origin/main,
review the transitive license changes, then run the attributions-rust and
attributions-python pre-commit hooks.

Files:

adapter-contract/python/pyproject.toml
pyproject.toml
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
Cargo.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

**/*.{py,pyi,rs,toml}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

**/*.{py,pyi,rs,toml}: - Python SDK or PyO3 binding changed
Use python-tests, run focused pytest tests first, then run
just test-python. Rebuild with just build-python when native code or
packaging changed.

Files:

adapter-contract/python/pyproject.toml
pyproject.toml
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
Cargo.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

**/*.{rs,toml,yml,yaml,sh,bash,zsh}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

**/*.{rs,toml,yml,yaml,sh,bash,zsh}: All source files must include an SPDX license header. Use the appropriate
comment syntax for the file type.

Files:

adapter-contract/python/pyproject.toml
pyproject.toml
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
Cargo.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

**/*.{rs,py,js,ts,tsx,html,md,mdx,toml,yml,yaml,sh,bash,zsh}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Reviewers will check SPDX headers during review.

Files:

adapter-contract/python/pyproject.toml
examples/harbor/swebench/README.md
pyproject.toml
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
examples/harbor/README.md
README.md
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
Cargo.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

**/{Cargo.toml,pyproject.toml,package.json}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Inspect the resolved transitive graph, not only the direct package license.

Files:

adapter-contract/python/pyproject.toml
adapter-contract/typescript/package.json
pyproject.toml
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
Cargo.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

**/*.{toml,lock,json}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Workspace, Python, and lockfile versions remain aligned where required

Files:

adapter-contract/python/pyproject.toml
adapter-contract/typescript/package.json
pyproject.toml
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
Cargo.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

**/*.{rs,py,pyi,ts,tsx,json,yaml,yml,md}

📄 CodeRabbit inference engine (.agents/skills/contribute-api/SKILL.md)

Start from the shared Rust core behavior first

Files:

adapter-contract/typescript/package.json
examples/harbor/swebench/README.md
examples/harbor/README.md
README.md

**/*.{rs,py,pyi,ts,tsx,json,yaml,yml}

📄 CodeRabbit inference engine (.agents/skills/contribute-api/SKILL.md)

**/*.{rs,py,pyi,ts,tsx,json,yaml,yml}: - Decide whether the CLI, PyO3 binding, Python SDK, type stubs, schemas, or the
Python and TypeScript adapter-contract bindings must expose the new surface

Keep every affected public surface in parity

Files:

adapter-contract/typescript/package.json

**/{package.json,npm-shrinkwrap.json,package-lock.json}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

**/{package.json,npm-shrinkwrap.json,package-lock.json}: - If the TypeScript manifest or npm lockfile changed, inspect the complete npm
dependency tree and license fields, confirm the package still has zero
production dependencies, run the attributions-node pre-commit hook, and run
its package and audit checks.

Files:

adapter-contract/typescript/package.json

**/*.{json,py,ts,tsx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

**/*.{json,py,ts,tsx}: Public contract changes must keep the
checked-in JSON Schema snapshots, Python representations, and generated
TypeScript declarations synchronized.

Files:

adapter-contract/typescript/package.json

**/*.{md,mdx,rst}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,mdx,rst}: For NeMo Fabric documentation, verify technical claims against the current repository, public API, or documented command before reviewing style.
Always spell NVIDIA in all caps; do not use Nvidia, nvidia, or NV.
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, parallel steps; split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English while preserving necessary technical precision.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once, and prefer refer to over see when directing readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical documentation.
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 commas in thousands.
Do not add trademark symbols to learning-oriented documentation unless the source, platform, or legal guidance explicitly requires them.
Do not replace precise technical terms with simpler words when doing so would lose precision.
Do not flag passive voice when the actor is unknown or the action is the important part.
Do not rewrite API names, package names, command flags, or code literals for style.

**/*.{md,mdx,rst}: Use consistent title case for technical-document headings and table headers; avoid quotation marks, ampersands, and exclamation marks in headings, while preserving official product, event, research, and whitepaper title ...

Files:

examples/harbor/swebench/README.md
examples/harbor/README.md
README.md

**/*.{md,rst,txt,adoc}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-language-mechanics.md)

**/*.{md,rst,txt,adoc}: For technical documentation, use professional, active, conversational, engaging, precise, and plain-English prose. Prefer active voice, present tense, short sentences, and scannable paragraphs. Avoid casual or imprecise language, swearing, threats, insults, jokes, puns, culture-specific idioms, marketing exaggeration, and unsupported third-party comparisons.
Use can for possibility and reserve may for permission; use after for temporal order; use refer to for cross-references; prefer short direct sentences and specific verbs; avoid unnecessary please in technical documentation.
Prefer active voice when the actor matters. Passive voice is acceptable when the actor is unknown or irrelevant, when the action or result is the focus, or in programmer documentation.
Use natural contractions in conversational technical prose, but do not force them in formal legal copy, API references, or generated text.
Prefer simpler English over Latinisms: use for example or such as instead of e.g., and so on instead of etc., that is instead of i.e., compared to instead of vs., and by, through, or using instead of via. Use industry-standard terms such as in silico, in vitro, and in vivo when appropriate, and italicize them in running text.
Use that without commas for essential clauses, and which with commas for nonessential clauses.
Format dates and times clearly: spell out months in body text; use forms such as June 12, 2025; avoid numeric or ordinal dates; capitalize days; use 12-hour time when appropriate; include a space before a.m. or p.m.; use ET and PT for needed time zones; avoid 24/7; and prefer from 12:30 to 1:00 p.m. for prose ranges.
Format numbers consistently: spell out zero through nine in body text, use numerals for 10 or greater and for technical values, use commas in thousands, do not begin a sentence with a numeral, spell out ordinals, and use numerals consistently within a category wh...

Files:

examples/harbor/swebench/README.md
examples/harbor/README.md
README.md

**/*.{md,mdx,yml,py,rs,sh}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

Keep documentation aligned with current NeMo Fabric behavior, repository layout, entry points, commands, package names, APIs, bindings, and support claims.

Files:

examples/harbor/swebench/README.md
examples/harbor/README.md
README.md

**/*.{md,mdx}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

**/*.{md,mdx}: Use the full product name NVIDIA NeMo Fabric on first use, typically in the title and H1; use NeMo Fabric thereafter. Use fabric alone only for the CLI tool and surround it with backticks.
Treat incorrect or stale commands, package names, paths, APIs, support claims, procedures, examples, terminology, or public behavior documentation as blocking issues.
Capitalize NVIDIA correctly and format code, commands, paths, and filenames as inline code where needed.
Use title case for technical-documentation headings.
Introduce code blocks, tables, and lists with complete lead-in sentences; ensure examples match current APIs and build commands.
Use descriptive anchor text, avoid raw URLs and generic labels such as here, and use repository-relative .mdx paths for links within docs/.
Prefer active voice, present tense, short sentences, plain English, consistent terminology, and imperative, parallel, scannable procedures.
Use after instead of once when expressing temporal sequence, and use can rather than may when describing possibility rather than permission.
Avoid ambiguous numeric dates and ordinal dates in body text.
For learning-oriented documentation, do not force trademark symbols unless the source document explicitly requires them.
When reporting documentation-review findings, lead with Must fix, Should fix, and Nice to have categories; include file path, line reference, current problem, rationale, and a concrete rewrite or direction.

Keep release-process and release-history policy in RELEASING.md, not in user-facing documentation or a duplicate CHANGELOG.md.

Update docs and examples in the same branch

**/*.{md,mdx}: - If documentation or examples changed, run just docs when practical and
verify documented commands against the current repository.

Documentation-only change
Use contribute-docs and review-doc-style. Run just docs for docs-site or
generated-reference changes.

**/*.{md,mdx}: If you...

Files:

examples/harbor/swebench/README.md
examples/harbor/README.md
README.md

**/*.{md,mdx,rst,yml,yaml,py,sh}

📄 CodeRabbit inference engine (.agents/skills/contribute-docs/SKILL.md)

**/*.{md,mdx,rst,yml,yaml,py,sh}: Keep package names, repository references, and build commands current.
Ensure example commands match current package names and paths.

Files:

examples/harbor/swebench/README.md
examples/harbor/README.md
README.md

**/*.{md,mdx,yml,yaml}

📄 CodeRabbit inference engine (.agents/skills/contribute-docs/SKILL.md)

**/*.{md,mdx,yml,yaml}: Update entry-point documentation, including README.md or docs/index.yml, when examples or reading paths change.
Update relevant getting-started, reference, entry-point, and example or adapter README documentation when examples or adapters change.

Files:

examples/harbor/swebench/README.md
examples/harbor/README.md
README.md

**/*.{md,mdx,rst,yml,yaml}

📄 CodeRabbit inference engine (.agents/skills/contribute-docs/SKILL.md)

Run just docs when the documentation site changes.

Files:

examples/harbor/swebench/README.md
examples/harbor/README.md
README.md

{docs,examples,adapters}/**/*

📄 CodeRabbit inference engine (.agents/skills/prepare-code-freeze/SKILL.md)

Update appropriate current-version installation, package, and configuration examples under docs, examples, and adapters from the old version to <next-version>, while preserving release notes, changelogs, generated output, and third-party attribution references.

Files:

examples/harbor/swebench/README.md
examples/notebooks/02_variations.ipynb
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
examples/harbor/README.md
examples/notebooks/01_quickstart.ipynb
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml

{adapters/**,examples/**}

⚙️ CodeRabbit configuration file

{adapters/**,examples/**}: Review adapter and example changes for command correctness, config/schema consistency, artifact handling, and compatibility with the public NeMo Fabric contracts.

Files:

examples/harbor/swebench/README.md
examples/notebooks/02_variations.ipynb
adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
examples/harbor/README.md
examples/notebooks/01_quickstart.ipynb
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml

{*.md,**/*.md,**/*.mdx,**/*.ipynb}

⚙️ CodeRabbit configuration file

{*.md,**/*.md,**/*.mdx,**/*.ipynb}: Enforce the product name in user-facing prose: use "NVIDIA NeMo Fabric" on first use and "NeMo Fabric" thereafter. Flag standalone capitalized "Fabric" when it refers to the product. Do not flag the lowercase fabric CLI command, package/import/crate names, code identifiers, API symbols, configuration keys, file paths, or unrelated generic uses of the word.

Files:

examples/harbor/swebench/README.md
examples/notebooks/02_variations.ipynb
examples/harbor/README.md
examples/notebooks/01_quickstart.ipynb
README.md

pyproject.toml

📄 CodeRabbit inference engine (.agents/skills/contribute-adapter/SKILL.md)

pyproject.toml: Add one canonical root extra that delegates to the matching leaf adapter
and its harness extra. Keep nemo-fabric-runtime an exact-version,
unconditional root dependency.

pyproject.toml: - The setuptools projects do not derive their versions from Cargo. Update the
literal project.version in every one of these files:

pyproject.toml

Keep internal Python package requirement pins aligned with the Python release
version:

All nemo-fabric-* == <version> requirements in the root
pyproject.toml optional dependencies.

pyproject.toml: The root project unconditionally depends on the exact-version
nemo-fabric-runtime distribution.
Each root harness extra delegates to the matching version of the leaf
adapter's harness extra.
Bare leaf dependencies remain adapter-owned, and the root adapter-tests
dependency group installs each leaf through its harness extra.
Every leaf provides full. Only adapters that import NeMo Relay Python APIs
provide relay; adapters that launch the Relay CLI install
nemo-relay-cli-bin through both harness and full.

Files:

pyproject.toml

{pyproject.toml,justfile}

📄 CodeRabbit inference engine (.agents/skills/contribute-adapter/SKILL.md)

{pyproject.toml,justfile}: Add the package to the root adapter-test dependency group,
[tool.uv.sources], python_projects in justfile, applicable catalogs,
and CI enumerations. Ship its descriptor under
share/nemo-fabric/adapters/<name>.

Files:

pyproject.toml

adapters/*/pyproject.toml

📄 CodeRabbit inference engine (.agents/skills/contribute-adapter/SKILL.md)

adapters/*/pyproject.toml: Give each Python leaf adapter a small base installation, a harness extra
for supported target packages, and a full extra for package-installable
integrations. Add a relay extra only when the adapter imports NVIDIA NeMo
Relay Python APIs.

Files:

adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml

adapters/**/pyproject.toml

📄 CodeRabbit inference engine (.agents/skills/update-project-version/SKILL.md)

adapters/**/pyproject.toml: - adapters/**/pyproject.toml

Each adapter's nemo-fabric-adapters-common == <version> dependency.

Files:

adapters/hermes/pyproject.toml
adapters/mini-swe-agent/pyproject.toml
adapters/codex/pyproject.toml
adapters/deepagents/pyproject.toml
adapters/common/pyproject.toml
adapters/claude/pyproject.toml

README.md

📄 CodeRabbit inference engine (.agents/skills/prepare-code-freeze/SKILL.md)

Update appropriate current-version installation, package, and configuration examples in README.md from the old version to <next-version>, while preserving intentional historical references.

Update user-facing entry points when public behavior, the nemo-fabric package (imported as nemo_fabric), examples, or supported bindings change: README.md, the Fern docs under docs/ (navigation in docs/index.yml, site config in fern/docs.yml), and the adapter/integration READMEs (adapters/*/README.md, python/src/nemo_fabric/integrations/*/README.md, examples/README.md).

Files:

README.md

{docs/**,README.md,AGENTS.md}

⚙️ CodeRabbit configuration file

{docs/**,README.md,AGENTS.md}: Review documentation for technical accuracy against the current API, command correctness, and consistency with generated schemas.
For links between files under docs/, require paths relative to the source file with the target file's .mdx extension so they work in both Fern builds and repository browsers. Flag Fern site-root links such as NeMo Fabric overview; use the repository-relative equivalent, such as NeMo Fabric overview.

Files:

README.md

Cargo.toml

📄 CodeRabbit inference engine (.agents/skills/update-project-version/SKILL.md)

Cargo.toml: - Cargo.toml [workspace.package].version is the source of truth for the Rust
workspace and the release version stamped into Python and TypeScript package
metadata.

Keep Cargo.toml [workspace.dependencies] self-references aligned when the
workspace version changes.

Run cargo check --workspace --locked.

Files:

Cargo.toml

🧠 Learnings (6)

📓 Common learnings

Learnt from: CR
Repo: NVIDIA/NeMo-Fabric PR: 0
File: .agents/skills/update-project-version/SKILL.md:0-0
Timestamp: 2026-08-14T17:12:48.852Z
Learning: Applies to adapters/**/pyproject.toml :   - Each adapter's `nemo-fabric-adapters-common == <version>` dependency.

Learnt from: CR
Repo: NVIDIA/NeMo-Fabric PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-08-14T17:10:55.809Z
Learning: Applies to README.md : - Update user-facing entry points when public behavior, the `nemo-fabric` package (imported as `nemo_fabric`), examples, or supported bindings change: `README.md`, the Fern docs under `docs/` (navigation in `docs/index.yml`, site config in `fern/docs.yml`), and the adapter/integration READMEs (`adapters/*/README.md`, `python/src/nemo_fabric/integrations/*/README.md`, `examples/README.md`).

📚 Learning: 2026-08-14T23:04:47.579Z

Learnt from: CR
Repo: NVIDIA/NeMo-Fabric PR: 0
File: .agents/skills/python-tests/SKILL.md:0-0
Timestamp: 2026-08-14T23:04:47.579Z
Learning: Applies to pyproject.toml : The root project unconditionally depends on the exact-version
  `nemo-fabric-runtime` distribution.

Applied to files:

pyproject.toml

📚 Learning: 2026-08-14T23:04:36.928Z

Learnt from: CR
Repo: NVIDIA/NeMo-Fabric PR: 0
File: .agents/skills/maintain-packaging/SKILL.md:0-0
Timestamp: 2026-08-14T23:04:36.928Z
Learning: Applies to **/pyproject.toml : Keep `nemo-fabric` as a metapackage that unconditionally installs the
  exact-version `nemo-fabric-runtime` distribution.

Applied to files:

pyproject.toml
sdk/python/nemo-fabric/pyproject.toml

📚 Learning: 2026-08-14T17:12:48.852Z

Learnt from: CR
Repo: NVIDIA/NeMo-Fabric PR: 0
File: .agents/skills/update-project-version/SKILL.md:0-0
Timestamp: 2026-08-14T17:12:48.852Z
Learning: Applies to pyproject.toml : - Keep internal Python package requirement pins aligned with the Python release
  version:

Applied to files:

pyproject.toml
adapters/mini-swe-agent/pyproject.toml

📚 Learning: 2026-08-14T17:12:48.852Z

Learnt from: CR
Repo: NVIDIA/NeMo-Fabric PR: 0
File: .agents/skills/update-project-version/SKILL.md:0-0
Timestamp: 2026-08-14T17:12:48.852Z
Learning: Applies to Cargo.toml : - Keep `Cargo.toml` `[workspace.dependencies]` self-references aligned when the
  workspace version changes.

Applied to files:

Cargo.toml

📚 Learning: 2026-08-14T17:12:48.852Z

Learnt from: CR
Repo: NVIDIA/NeMo-Fabric PR: 0
File: .agents/skills/update-project-version/SKILL.md:0-0
Timestamp: 2026-08-14T17:12:48.852Z
Learning: Applies to Cargo.toml : - `Cargo.toml` `[workspace.package].version` is the source of truth for the Rust
  workspace and the release version stamped into Python and TypeScript package
  metadata.

Applied to files:

Cargo.toml

🔇 Additional comments (16)

Cargo.toml (1)

17-23: LGTM!

pyproject.toml (1)

11-11: LGTM!

sdk/python/nemo-fabric/pyproject.toml (1)

12-12: LGTM!

Also applies to: 28-28, 53-65, 74-74

README.md (1)

164-164: LGTM!

Also applies to: 184-184, 204-204

examples/harbor/README.md (1)

70-77: LGTM!

examples/harbor/swebench/README.md (1)

30-30: LGTM!

examples/notebooks/01_quickstart.ipynb (1)

109-109: LGTM!

examples/notebooks/02_variations.ipynb (1)

98-98: LGTM!

adapter-contract/python/pyproject.toml (1)

12-12: LGTM!

adapter-contract/typescript/package.json (1)

3-3: LGTM!

adapters/common/pyproject.toml (1)

12-12: LGTM!

adapters/claude/pyproject.toml (1)

12-12: LGTM!

Also applies to: 28-29

adapters/codex/pyproject.toml (1)

12-12: LGTM!

Also applies to: 28-29

adapters/deepagents/pyproject.toml (1)

12-12: LGTM!

Also applies to: 28-29

adapters/hermes/pyproject.toml (1)

12-12: LGTM!

Also applies to: 29-30

adapters/mini-swe-agent/pyproject.toml (1)

12-12: LGTM!

Also applies to: 28-29

Walkthrough

NeMo Fabric package metadata, internal dependency pins, workspace requirements, and installation documentation were updated from version 0.2.0 to 0.3.0.

Changes

Version alignment

Layer / File(s)	Summary
Workspace and SDK metadata `Cargo.toml`, `pyproject.toml`, `sdk/python/nemo-fabric/pyproject.toml`	Workspace, runtime, SDK, and adapter dependency versions now use 0.3.0.
Contract and adapter packages `adapter-contract/`, `adapters/`	Contract and adapter package versions and internal dependency pins now use 0.3.0.
Documentation and examples `README.md`, `examples/harbor/`, `examples/notebooks/`	Installation instructions and examples now reference version 0.3.0.

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

Merge Risk: ⚪ Minimal · up to 86729

This PR advances development versions and updates corresponding package, lockfile, and documentation references; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Title check	✅ Passed	The title follows Conventional Commits format and accurately describes the 0.2 code-freeze preparation.
Description check	✅ Passed	The description includes the overview, review starting point, related-issues section, checklists, implementation details, and validation steps.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

github-actions · 2026-08-15T01:13:41Z

Fern docs preview: https://nvidia-preview-pull-request-239.docs.buildwithfern.com/nemo/fabric

AnuradhaKaruppiah · 2026-08-15T01:26:48Z

/merge

chore: prepare 0.2 code freeze

86729bb

Signed-off-by: Anuradha Karuppiah <26330987+AnuradhaKaruppiah@users.noreply.github.com>

copy-pr-bot Bot temporarily deployed to fern August 15, 2026 01:10 Inactive

AnuradhaKaruppiah marked this pull request as ready for review August 15, 2026 01:14

AnuradhaKaruppiah requested a review from a team as a code owner August 15, 2026 01:14

AnuradhaKaruppiah merged commit 3a9fcf7 into NVIDIA:main Aug 15, 2026
39 checks passed

AnuradhaKaruppiah temporarily deployed to fern August 15, 2026 01:31 — with GitHub Actions Inactive

Navigation Menu

Uh oh!

chore: prepare 0.2 code freeze - #239

chore: prepare 0.2 code freeze#239
AnuradhaKaruppiah merged 1 commit into
NVIDIA:mainfrom
AnuradhaKaruppiah:docs/code-freeze-0.2

AnuradhaKaruppiah commented Aug 15, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

coderabbitai Bot commented Aug 15, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Aug 15, 2026

Uh oh!

AnuradhaKaruppiah commented Aug 15, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

AnuradhaKaruppiah commented Aug 15, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Overview

Details

Validation

Where should the reviewer start?

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

Summary by CodeRabbit

Uh oh!

coderabbitai Bot commented Aug 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

github-actions Bot commented Aug 15, 2026

Uh oh!

AnuradhaKaruppiah commented Aug 15, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

AnuradhaKaruppiah commented Aug 15, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Aug 15, 2026 •

edited

Loading