chore: clear release notes and migration guide for 0.7

[willkill07]

Overview

Prepare the repository for the upcoming 0.7 release.

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

Details

• Stop nightly alpha tag creation for release/0.6.
• Replace 0.6-specific release-note highlights and fixed issues with 0.7 placeholders.
• Carry forward known issues and update the migration reference to 0.6 to 0.7.

Where should the reviewer start?

Review .github/nightly-alpha-branches.yaml for the nightly-tag change, then docs/about-nemo-relay/release-notes/index.mdx for the 0.7 release-note structure.

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

• Relates to: none

Summary by CodeRabbit

• Documentation
  • Updated NVIDIA NeMo Relay release notes to document version 0.7 (including placeholders for Highlights and Fixed Known Issues).
  • Updated migration guidance to reference upgrading 0.6 → 0.7, replacing detailed 0.6 content with a 0.7 placeholder.
• Chores
  • Adjusted nightly alpha branch configuration to remove the release/0.6 branch, leaving main only.

[coderabbitai]

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: ba26c0e8-ff03-4100-961a-f470da2ab47b

📥 Commits

Reviewing files that changed from the base of the PR and between 9825791 and ccc491f.

📒 Files selected for processing (2)

• docs/about-nemo-relay/release-notes/index.mdx
• docs/reference/migration-guides.mdx

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (8)

**/*.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/reference/migration-guides.mdx
• docs/about-nemo-relay/release-notes/index.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 as RELEASING.md, not as user-facing docs pages or CHANGELOG.md
Keep stable user-facing wrappers at scripts/ 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, and grpc-v1 protocol details on separate pages

If links in documentation change, run just docs-linkcheck.

Files:

• docs/reference/migration-guides.mdx
• docs/about-nemo-relay/release-notes/index.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/reference/migration-guides.mdx
• docs/about-nemo-relay/release-notes/index.mdx

{docs,examples}/**/*

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update docs and examples.

Files:

• docs/reference/migration-guides.mdx
• docs/about-nemo-relay/release-notes/index.mdx

**/*

📄 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, use maintain-dynamic-plugins and 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, prefer uv run pre-commit run --files <changed files...>.
Before review or handoff, run uv run pre-commit run --all-files.

Files:

• docs/reference/migration-guides.mdx
• docs/about-nemo-relay/release-notes/index.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/reference/migration-guides.mdx
• docs/about-nemo-relay/release-notes/index.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/reference/migration-guides.mdx
• docs/about-nemo-relay/release-notes/index.mdx

docs/about-nemo-relay/release-notes/{index,highlights,known-issues}.mdx

📄 CodeRabbit inference engine (.agents/skills/draft-release-notes/SKILL.md)

docs/about-nemo-relay/release-notes/{index,highlights,known-issues}.mdx: Update only docs/about-nemo-relay/release-notes/index.mdx, docs/about-nemo-relay/release-notes/highlights.mdx, and docs/about-nemo-relay/release-notes/known-issues.mdx unless the release changes their route or entry points.
Preserve the existing MDX front matter and the JSX SPDX comment in the release-notes pages.

Files:

• docs/about-nemo-relay/release-notes/index.mdx

🔇 Additional comments (2)

docs/about-nemo-relay/release-notes/index.mdx (1)

4-4: LGTM!

Also applies to: 28-34, 43-50

docs/reference/migration-guides.mdx (1)

9-16: LGTM!

---

Walkthrough

Nightly alpha tracking now targets only main. Release notes and migration documentation were advanced from NeMo Relay 0.6 to 0.7, replacing prior detailed guidance with placeholders for forthcoming release information.

Changes

Release 0.7 Transition

Layer / File(s)	Summary
Nightly alpha branch tracking .github/nightly-alpha-branches.yaml	Removes release/0.6, leaving main as the only nightly alpha branch.
Release 0.7 release notes docs/about-nemo-relay/release-notes/index.mdx	Updates metadata, release headings, migration text, and fixed-issue sections to 0.7, with placeholders for highlights and fixed issues.
Release 0.7 migration guidance docs/reference/migration-guides.mdx	Changes the upgrade plan to 0.6-to-0.7 and replaces detailed 0.6 guidance with a 0.7 placeholder.

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

Possibly related PRs

• NVIDIA/NeMo-Relay#538: Updates the same release documentation surfaces from version 0.6 to 0.7.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The Conventional Commits title is valid and accurately summarizes the 0.7 release-note prep changes.
Description check	✅ Passed	All required sections are present and the PR purpose, details, and reviewer start point are clear; the related issue line is only a placeholder.
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

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/about-nemo-relay/release-notes/index.mdx`:
- Line 46: Update the migration guidance referenced by the release notes so it
documents the 0.6→0.7 upgrade before linking users to it, replacing or extending
the existing 0.5→0.6 coverage in the migration guide. If that guidance is not
ready, remove or defer the 0.6→0.7 release-note claim instead of linking to
obsolete instructions.

🪄 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: 0e013d82-a87f-4304-8a38-f8c714333d18

📥 Commits

Reviewing files that changed from the base of the PR and between cd46f56 and 9825791.

📒 Files selected for processing (2)

• .github/nightly-alpha-branches.yaml
• docs/about-nemo-relay/release-notes/index.mdx

💤 Files with no reviewable changes (1)

• .github/nightly-alpha-branches.yaml

📜 Review details

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

• GitHub Check: Check / Run
• GitHub Check: Preview docs

🧰 Additional context used

📓 Path-based instructions (8)

**/*.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/about-nemo-relay/release-notes/index.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 as RELEASING.md, not as user-facing docs pages or CHANGELOG.md
Keep stable user-facing wrappers at scripts/ 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, and grpc-v1 protocol details on separate pages

If links in documentation change, run just docs-linkcheck.

Files:

• docs/about-nemo-relay/release-notes/index.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/about-nemo-relay/release-notes/index.mdx

docs/about-nemo-relay/release-notes/{index,highlights,known-issues}.mdx

📄 CodeRabbit inference engine (.agents/skills/draft-release-notes/SKILL.md)

docs/about-nemo-relay/release-notes/{index,highlights,known-issues}.mdx: Update only docs/about-nemo-relay/release-notes/index.mdx, docs/about-nemo-relay/release-notes/highlights.mdx, and docs/about-nemo-relay/release-notes/known-issues.mdx unless the release changes their route or entry points.
Preserve the existing MDX front matter and the JSX SPDX comment in the release-notes pages.

Files:

• docs/about-nemo-relay/release-notes/index.mdx

{docs,examples}/**/*

📄 CodeRabbit inference engine (.agents/skills/rename-surfaces/SKILL.md)

Update docs and examples.

Files:

• docs/about-nemo-relay/release-notes/index.mdx

**/*

📄 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, use maintain-dynamic-plugins and 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, prefer uv run pre-commit run --files <changed files...>.
Before review or handoff, run uv run pre-commit run --all-files.

Files:

• docs/about-nemo-relay/release-notes/index.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/about-nemo-relay/release-notes/index.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/about-nemo-relay/release-notes/index.mdx

🔇 Additional comments (1)

docs/about-nemo-relay/release-notes/index.mdx (1)

4-4: LGTM!

Also applies to: 28-34, 48-50

[github-actions]

Fern docs preview: https://nvidia-preview-pull-request-544.docs.buildwithfern.com/nemo/relay/dev

[willkill07]

/merge