Forward-merge release/0.3 into main#190
Merged
Merged
Conversation
#### Overview
Documentation cleanup that removes stale "NeMo Flow" / "NAT" / "NeMo Agent
Toolkit" naming in favor of the current project name (NeMo Relay), refreshes the
Quick Start landing page with per-binding navigation, and corrects a few stale
integration notes. Docs-only; no runtime or public API behavior changes.
- [x] I confirm this contribution is my own work, or I have the right to submit it under this project's license.
- [x] I searched existing issues and open pull requests, and this does not duplicate existing work.
#### Details
- Quick Start (`docs/getting-started/quick-start/index.mdx`): add a 3-column
`CardGroup` linking to the Python, Node.js, and Rust Quick Start guides.
- Correct stale naming to "NeMo Relay":
- `.github/CODE_OF_CONDUCT.md`: title is now "NVIDIA NeMo Relay Code of Conduct".
- `README.md`, `docs/integrate-into-frameworks/about.mdx`,
`docs/integrate-into-frameworks/non-serializable-data.mdx`,
`docs/nemo-relay-cli/hermes.mdx`, `docs/resources/support-and-faqs.mdx`:
replace leftover "NeMo Flow" references with "NeMo Relay".
- `docs/about-nemo-relay/ecosystem.mdx`: rename the `Flow` node to `Relay` in
the architecture mermaid diagram.
- `AGENTS.md`: refresh the public-API integration notes to list LangGraph and
Deep Agents alongside LangChain, and point to `docs/supported-integrations/`
and `python/tests/integrations/`.
- `integrations/coding-agents/README.md`: remove the stale `hermes/` native
plugin bundle bullet.
#### Where should the reviewer start?
Start with the naming corrections, especially `.github/CODE_OF_CONDUCT.md` (it
was mistakenly set to "NeMo Flow") and the mermaid node rename in
`docs/about-nemo-relay/ecosystem.mdx`. Then review the new `CardGroup` in
`docs/getting-started/quick-start/index.mdx`. Validated with `just docs-linkcheck`
(0 errors; the only warning is the auth-gated redirects check being skipped).
#### Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)
- Relates to: none
## Summary by CodeRabbit
* **New Features**
* Added interactive quick-start cards for Python, Node.js, and Rust linking to language guides.
* **Documentation**
* Broadened public integrations list to include LangGraph and Deep Agents.
* Standardized product name/terminology from “Flow” to “Relay” across docs and diagrams.
* Clarified framework boundary guidance and non-serializable data wording.
* Updated Hermes agent guidance and support/FAQ wording.
* Adjusted Hermes packaging guidance in integrations docs.
[](https://app.coderabbit.ai/change-stack/NVIDIA/NeMo-Relay/pull/188?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack)
Authors:
- Zhongxuan (Daniel) Wang (https://github.com/zhongxuanwang-nv)
Approvers:
- Will Killian (https://github.com/willkill07)
URL: #188
Author
|
SUCCESS - forward-merge complete. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Forward-merge triggered by push to release/0.3 that creates a PR to keep main up-to-date. If this PR is unable to be immediately merged due to conflicts, it will remain open for the team to manually merge. See forward-merger docs for more info.