fix: constrain Hermes Relay compatibility

[zhongxuanwang-nv]

Overview

Constrain the Hermes adapter's relay and full extras to NeMo Relay 0.6.x.

A live Hermes Agent 0.19.0 + NeMo Relay 0.7.2 run returned the correct model response, but generated no Relay artifacts. Relay 0.7 rejected Hermes' generated v3 plugin configuration; Hermes failed open, so the integration looked successful while exporting no telemetry. Hermes 0.19.0 is the only published compatible Hermes Agent release, and the supported Relay 0.6.0 combination produces both ATOF and ATIF artifacts in a fresh live run.

This aligns the Hermes leaf adapter with the root project's existing nemo-relay>=0.6.0,<0.7 constraint. It is intentionally limited to dependency metadata, the regenerated lock, and its metadata expectation; no runtime code changes.

Details

• Change nemo-relay>=0.6.0,<0.8 to nemo-relay>=0.6.0,<0.7 for both relay and full extras.
• Regenerate the Hermes adapter lockfile, resolving NeMo Relay 0.6.0.
• Update the adapter metadata assertion.
• Relay 0.7 support can be restored when a released Hermes Agent version supports its configuration contract and passes live end-to-end export validation.

Exact Relay 0.7.2 configuration and responses

This is the exact plugins.toml emitted by the Hermes adapter in a clean Relay 0.7.2 reproduction of the ATOF+ATIF configuration (including its emitted local paths):

version = 1

[[components]]
kind = "observability"
enabled = true

[components.config]
version = 3

[components.config.atif]
enabled = true
output_directory = "/private/tmp/nemo-fabric-hermes-relay07-pr.EoDqG8/artifacts/relay/relay07-pr-repro"
filename_template = "trajectory-{session_id}.atif.json"
agent_name = "code-review-agent"
agent_version = "fabric-sdk-example"
model_name = "nvidia/nemotron-3-nano-omni-30b-a3b-reasoning"

[components.config.atof]
enabled = true

[[components.config.atof.sinks]]
type = "file"
output_directory = "/private/tmp/nemo-fabric-hermes-relay07-pr.EoDqG8/artifacts/relay/relay07-pr-repro"
filename = "events.atof.jsonl"
mode = "append"

Relay's plugin.validate() response for that parsed TOML was exactly:

{"diagnostics":[]}

Relay's plugin.initialize() response for the same parsed TOML was exactly:

RuntimeError: invalid config: OpenTelemetry mark_projection moved into each typed endpoint in observability config version 3; OpenTelemetry transport moved into each typed endpoint in observability config version 3; OpenTelemetry endpoint moved into each typed endpoint in observability config version 3; OpenTelemetry headers moved into each typed endpoint in observability config version 3; OpenTelemetry resource_attributes moved into each typed endpoint in observability config version 3; OpenTelemetry service_name moved into each typed endpoint in observability config version 3; OpenTelemetry service_namespace moved into each typed endpoint in observability config version 3; OpenTelemetry instrumentation_scope moved into each typed endpoint in observability config version 3; OpenTelemetry timeout_millis moved into each typed endpoint in observability config version 3; enabled OpenTelemetry section requires at least one endpoint

The original live Hermes Agent 0.19.0 + Relay 0.7.2 model run returned:

input: Reply with exactly: RELAY_ZERO_SEVEN_OK
status: succeeded
response: RELAY_ZERO_SEVEN_OK
relay_artifacts: []

Validation

• .venv/bin/python -m pytest -q tests/adapters/test_adapter_package_metadata.py — 18 passed
• uv lock --check --project adapters/hermes
• Built the Hermes adapter wheel and verified its relay and full METADATA each require nemo-relay<0.7,>=0.6.0
• uv run --no-project python scripts/licensing/license_diff.py --base-ref upstream/main — no license changes
• pre-commit run --all-files attributions-python and attributions-rust
• Fresh live NVIDIA API smoke with Hermes Agent 0.19.0 + NeMo Relay 0.6.0 — succeeded with 7 ATOF records and both ATOF/ATIF artifact kinds
• Clean isolated NeMo Relay 0.7.2 reproduction — captured the emitted plugin TOML and full plugin.validate() / plugin.initialize() responses above

Where should the reviewer start?

Start with adapters/hermes/pyproject.toml; adapters/hermes/uv.lock is the corresponding resolution update.

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

• Relates to feat(hermes): use upstream Relay integration #192

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

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 49f6b572-f6b3-4fd8-89b1-fcb788798154

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

Walkthrough

The Hermes adapter now restricts nemo-relay to versions from 0.6.0 up to, but not including, 0.7. The package metadata test now checks the updated constraint.

Changes

Hermes relay dependency

Layer / File(s)	Summary
Dependency bound and metadata validation adapters/hermes/pyproject.toml, tests/adapters/test_adapter_package_metadata.py	The relay and full optional dependency groups now require nemo-relay>=0.6.0,<0.7. The metadata test expects the same constraint.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• NVIDIA/NeMo-Fabric#192: Directly related changes to the Hermes Relay dependency range and its metadata test.

🚥 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 uses valid Conventional Commits format and clearly describes the dependency compatibility change.
Description check	✅ Passed	The description includes the required overview, reviewer starting point, related issue, confirmations, and detailed validation information.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[github-actions]

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

[zhongxuanwang-nv]

/merge