Repository navigation
chore(deps): update pinned tools, images, Hermes Agent and OpenTofu - #14481
Merged
Merged
Conversation
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Collaborator
Author
Authoring session — opening
Cutoff: 2026-11-16T09:41Z. |
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Contributor
|
v1 documentation preview: https://nvidia-preview-nemoclaw-v1-pr-14481.docs.buildwithfern.com/nemoclaw |
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
added a commit
that referenced
this pull request
Nov 16, 2026
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>
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.
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
versions.json, the test modules'required_version, docs that name the versionversions.json, CI runner tests, docsversions.json,image/ollama, runtime comments and docsversions.jsonsource archive,HERMES_IMAGE,HERMES-NOTICE.md, docsversions.json,image/NOTICE.md, docsNODE_IMAGE, the docs workflow, docsUV_IMAGEruff.toml, the image lint stage, docsfern/fern.config.jsonregistry:3registry:3jsonschemaCargo.tomlnemo-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_IMAGEpins Docker Hub'sv0.22.7digest, the same release as the source archive; the image build compares the two.fit_params_targetis still 1024 MiB, and still readsOLLAMA_GPU_OVERHEADas before, so the runtime's GPU reserve logic is unchanged; the comments and inference guide now name v0.40.16 and b12177.>=24.22.1 <25 || >=26.12.1, and Fabric's TypeScript adapters need 22.19 or newer. Node.js 26's binary linkslibatomic.so.1, which the agent images' Python base lacks, so the base installs Debian'slibatomic1besidelibstdc++6; without it,nodedoesn't start and OpenClaw's runtime fails at start.Left as they are:
pulldown-cmark-to-cmark23 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-cachev2.9.3 (d1527c8) andtaiki-e/install-actionv2.90.5 (ab49d3c) wait for an organization admin to allow their commits; until then a workflow that names them doesn't start.stable-alpine,docker/dockerfile:1,schemars,pulldown-cmark, the other GitHub Actions, andtf-provider's pinned commit.bollard-stubsmust equal whatbollard0.21.1 requires.