Skip to content

chore(deps): update pinned tools, images, Hermes Agent and OpenTofu - #14481

Merged
cv merged 6 commits into
v1from
cv/deps-2026-11
Nov 16, 2026
Merged

cv merged 6 commits into
v1from
cv/deps-2026-11

Conversation

@cv

@cv cv commented Nov 16, 2026 •

Copy link
Copy Markdown
Collaborator

Updates NemoClaw's pinned tools, images and agent sources to their latest stable releases, except where a component they must match limits the version. Bundles, agent images and CI built from this revision use OpenTofu 1.13.9, Hermes Agent v0.22.7 with the Switchyard Relay plugin 0.3.2, Ollama 0.40.16, and Node.js 26 LTS.

Problem

Several pins trail their latest stable release, some by a minor version: OpenTofu 1.12.12 (1.13.9), Hermes Agent v0.22.5 (v0.22.7, the newest the pinned Fabric's Hermes adapter supports), Node.js 24.22.2 (26.13.1 LTS), Ollama 0.40.14 (0.40.16), and several CI tools, actions and base images.

Change

Pin Old New Where
OpenTofu 1.12.12 1.13.9 versions.json, the test modules' required_version, docs that name the version
cargo-nextest 0.9.151 0.9.152 versions.json, CI runner tests, docs
Ollama 0.40.14 0.40.16 versions.json, image/ollama, runtime comments and docs
Hermes Agent v0.22.5 v0.22.7 versions.json source archive, HERMES_IMAGE, HERMES-NOTICE.md, docs
Switchyard Relay plugin 0.3.1 0.3.2 versions.json, image/NOTICE.md, docs
Node.js 24.22.2 26.13.1 LTS NODE_IMAGE, the docs workflow, docs
uv 0.13.7 0.13.8 UV_IMAGE
Ruff 0.16.7 0.17.5 ruff.toml, the image lint stage, docs
Fern CLI 5.92.4 5.216.0 fern/fern.config.json
Syft v1.55.0 v1.57.1 image and release workflows, docs
Grype 0.121.0 0.121.3 release assessment action, vulnerability monitor, scanner version, docs
BuildKit (digest) v0.35.0 Brev and release workflows
registry:3 (digest) current registry:3 kind registry
jsonschema =0.56.0 =0.61.2 Cargo.toml
  • Hermes and Relay move together. At the pinned Fabric revision, the Hermes adapter supports Hermes v0.22.5 (Relay 0.10) and v0.22.7 (Relay 0.11). Hermes v0.22.7 requires nemo-relay>=0.11,<0.12; the Switchyard plugin 0.3.1 requires Relay <0.11, and 0.3.2 accepts >=0.10.1,<1.0.0. HERMES_IMAGE pins Docker Hub's v0.22.7 digest, the same release as the source archive; the image build compares the two.
  • Ollama: v0.40.16 builds llama.cpp b12177, whose fit_params_target is still 1024 MiB, and still reads OLLAMA_GPU_OVERHEAD as before, so the runtime's GPU reserve logic is unchanged; the comments and inference guide now name v0.40.16 and b12177.
  • Node.js 26: OpenClaw 2026.9.34 accepts >=24.22.1 <25 || >=26.12.1, and Fabric's TypeScript adapters need 22.19 or newer. Node.js 26's binary links libatomic.so.1, which the agent images' Python base lacks, so the base installs Debian's libatomic1 beside libstdc++6; without it, node doesn't start and OpenClaw's runtime fails at start.
  • Checksums: OpenTofu, Grype and the Docker images come from the releases' published checksums and registry digests; nextest, the Hermes source archive and the Switchyard bundles were hashed after download.

Left as they are:

  • Fabric stays at feat: load skills from directories with bundled and duplicate controls NeMo-Fabric#632's head, which is still open; OpenClaw stays at 2026.9.34, the only version that Fabric's adapter accepts; Python stays at 3.14.10, because Fabric's Hermes extra requires Python below 3.15.
  • Agent Sandbox stays at 1.0.3 (1.0.11 is out): NemoClaw tests the version OpenShell v0.1.8's Kubernetes tests use.
  • Rust 1.100.0 and pulldown-cmark-to-cmark 23 need code changes, so they get their own pull requests. The Docker provider 4.7.0 moves in its own pull request with the code it lets NemoClaw delete. vLLM v0.33.0 is left for a pull request qualified on GPU hardware.
  • Swatinem/rust-cache v2.9.3 (d1527c8) and taiki-e/install-action v2.90.5 (ab49d3c) wait for an organization admin to allow their commits; until then a workflow that names them doesn't start.
  • Already latest: kind 0.33.0, protoc 36.2, the Helm provider 3.3.0, Bun 1.4.4, Brev CLI 0.6.337, PyYAML 6.0.3, cargo-llvm-cov 0.9.1, nginx-unprivileged stable-alpine, docker/dockerfile:1, schemars, pulldown-cmark, the other GitHub Actions, and tf-provider's pinned commit. bollard-stubs must equal what bollard 0.21.1 requires.

cv added 2 commits November 16, 2026 02:37
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
@cv

cv commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator Author
Authoring session — opening
Field Status Value Evidence or limit
Harness partial Pi (Pit TypeScript tool) Session header records the session schema and working directory, not the Pi version
Skills recorded test-driven-development (complete read); write-tests (complete read); nemoclaw-contributor-create-pr (complete read, in two reads) Skill reads to cutoff
Instruction files partial AGENTS.md (injected); WRITING.md, internal-docs/design/scope.md, internal-docs/contributing/agent-image-maintenance.md, .github/PULL_REQUEST_TEMPLATE.md, .github/SESSION_REPORT_TEMPLATE.md (complete reads); internal-docs/contributing/testing.md (partial read) Injections and reads to cutoff; testing.md's middle sections were truncated in the record
Tool calls partial typescript: 197 Includes failed calls; the TypeScript wrapper hides its nested host calls
Tokens recorded input: 45410907; cached input: 45038595; output: 127274 Sum of assistant message usage to cutoff (input + cacheRead + cacheWrite; cacheRead; output)
Session window recorded 2026-11-16T08:58Z to 2026-11-16T09:41Z; 42 min First event to cutoff, including idle time; the session also authored the other dependency PRs
Compactions recorded 0 Complete record to cutoff; context elisions are not compactions
Models recorded azure/anthropic/claude-opus-5-5 Model change events; no later changes
Reasoning levels recorded high Thinking-level change events

Cutoff: 2026-11-16T09:41Z.

Signed-off-by: Carlos Villela <cvillela@nvidia.com>
@github-actions

Copy link
Copy Markdown
Contributor

cv added 3 commits November 16, 2026 03:02
Signed-off-by: Carlos Villela <cvillela@nvidia.com>

# Conflicts:
#	docs/about/release-notes.md
#	versions.json
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
@cv
cv merged commit fc50f2f into v1 Nov 16, 2026
64 checks passed
@cv
cv deleted the cv/deps-2026-11 branch November 16, 2026 10:39
cv added a commit that referenced this pull request Nov 16, 2026
Move the release notes that reached v1 after the v0.1.0-rc10 tag (#14480, #14481, #14482, #14483) into the sections since v0.1.0-rc10.

Signed-off-by: Carlos Villela <cvillela@nvidia.com>
cv added a commit that referenced this pull request Nov 16, 2026
The v1 release notes now list `v0.1.0-rc10`'s changes under their own
headings and start "since `v0.1.0-rc10`" sections, so contributors add
new entries there and readers can tell what the release candidate
contains.

## Problem

`docs/about/release-notes.md` lists everything that reached `v1` after
the `v0.1.0-rc9` tag under "Changes Since v0.1.0-rc9". `v0.1.0-rc10` is
being tagged on 5716c39 (#14429), so those entries are now rc10's
contents, and later changes need a separate place. rc9 left no
per-candidate section, so this sets the convention.

## Change

- "Product Changes" gets a "Changes Since v0.1.0-rc10" section, followed
by "Changes in v0.1.0-rc10", which keeps the existing entries and says
they reached `v1` between the `v0.1.0-rc9` and `v0.1.0-rc10` tags.
- "Breaking Changes and Migration" keeps its general intro and gets
matching "Breaking Changes Since v0.1.0-rc10" and "Breaking Changes in
v0.1.0-rc10" sections; the existing list moves under the latter
unchanged.
- The entries labeled "Earlier changes" (`updatePolicy: Preserve` and
the removed `spec.gateway.image`) were already in `v0.1.0-rc9`, so they
get an "Earlier Breaking Changes" heading instead of falling under
rc10's.
- Each intro links to its matching breaking-changes section. No other
page links to the old `#changes-since-v010-rc9` anchor,
`#breaking-changes-and-migration` still exists, and no contributing
guide names the section.
- The entries that #14480, #14481, #14482, and #14483 added after the
`v0.1.0-rc10` tag move to the sections since `v0.1.0-rc10`, so those
sections no longer say "None yet." The rc10 sections match
`v0.1.0-rc10:docs/about/release-notes.md`, including its pinned
component versions.
- The statement that v1 has no release yet stays: release-candidate tags
stage private drafts.

Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant