Repository navigation
docs: list v1 changes since v0.1.0-rc9 and correct stale example claims - #14413
Merged
Merged
Conversation
Collaborator
Author
Authoring session — opening
|
Contributor
|
v1 documentation preview: https://nvidia-preview-nemoclaw-v1-pr-14413.docs.buildwithfern.com/nemoclaw |
Collaborator
Author
Authoring session — commit 362c75f
|
cv
enabled auto-merge (squash)
November 11, 2026 17:44
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.
The release notes now list every user-visible change on
v1since thev0.1.0-rc9tag, including the breaking ones, and four example pages drop claims that later changes made false.Problem
docs/about/release-notes.mdlisted three breaking changes and none of the features, fixes, and onboarding changes that reachedv1afterv0.1.0-rc9; it didn't name the configuration shapes the parser now rejects or the intent record versionv0.1.0-rc9writes.Some example claims went stale:
examples/spark/README.mdsaid the pinned OpenShell has the Podman TLS initialization blocker, bug(podman): unprivileged supervisor cannot initialize TLS CA, blocking provider traffic OpenShell#3427; its fix merged before OpenShell 0.1.0, andv1pins 0.1.7.examples/station/README.mdandexamples/gtc-dc/README.mdrequired exactly one visible GPU on the host; since fix(inference): let a managed model service name the GPU it uses #13929,container.gpuDeviceslets a service on a host with more GPUs request one.examples/hcl/travel-teamsaid Fabric's Deep Agents adapter can't turn reasoning off, Deep Agents adapter: no way to set a model's reasoning effort NeMo-Fabric#433; fix(deepagents): support configured reasoning effort NeMo-Fabric#439 fixed that, and the pinned catalog's Deep Agentsreasoning_effortacceptsnone.openshell_apilanded.Change
docs/about/release-notes.mdgains "Changes Since v0.1.0-rc9", grouped by area, from the commits inv0.1.0-rc9..origin/v1; where a later commit changed an earlier one, the entry describes the current code, and changes added and removed after the tag aren't listed:versions.jsonandimage/fabric/Dockerfile.v0.1.0-rc9writes, through 16 (fix(state)!: refuse another release's state by its intent record version #14266), 17 (feat(policy)!: accept OpenShell network middleware bindings in sandbox policies #14343), 18 (fix(inference): let a managed model service name the GPU it uses #13929), 19 (feat(inference): set vLLM's tensor and pipeline parallel sizes #14391) and 20 (fix(inference): drop the recipe GPU count #14394);sandboxesandinferenceProviders(refactor(config)!: key inference providers by name #13703, refactor(config)!: key sandboxes by name #13705);compatibility.gpuoutside every hardware profile (fix(vllm): check a dedicated-memory recipe's GPU budget against GPU memory #13912);max_tokenslosing its default (feat(fabric)!: accept a skill folder or a folder of skills in skills.paths #14296);skills.pathsresolution (feat(fabric)!: accept a skill folder or a folder of skills in skills.paths #14296);networkCIDRvalidation (fix(backend): validate the endpoint host the client connects to #13847, fix: reject metadata hosts, IPv4-embedding IPv6 hosts, and non-canonical networks #14081);gateway_valuesattribute (feat(kubernetes): let OpenShift assign the managed gateway's UID #14014), and Kubernetes ownership receipts from before feat(kubernetes): bind an existing namespace by UID and drop cluster-wide reads #13922 and feat(kubernetes): let OpenShift assign the managed gateway's UID #14014.The two earlier items stay, under their own heading.
examples/spark/README.mdreplaces the closed OpenShell#3427 blocker with the Podman and remote-model limits indocs/resources/limits.md.examples/station/README.mdandexamples/gtc-dc/README.mdrequire one GPU visible in the model container, and point tocontainer.gpuDevicesfor a host with more.examples/hcl/travel-team/README.mdandWALKTHROUGH.mddrop the NeMo-Fabric#433 limitation, and the travel team's booking-key statements link Send the travel team buyer's booking key to its MCP server #14417 instead of A credential type for APIs other than inference and web search #13313.Not listed, because both changes landed after the tag: Deep Agents Code (#14043, #14250),
compatibility.gpuCount(#14391, #14394), and the "Creating infrastructure state" progress step (#14169, #14248).Checked and left unchanged: the root
README.md,crates/nemoclaw-onboarding/README.md,crates/nemoclaw-cli/assets/README.md,internal-docs/README.md, the other example READMEs, and every example YAML header comment. The GPU autoscaling README andload.shread the JSON fieldsOperationResultserializes, and NVIDIA/OpenShell#4287 is fixed only after the pinned 0.1.7. The two pre-tag release-note items still match the schema and SDK.docs/README.mdis left to #14412, which retires the stale field reference snapshot it describes.Not verified: whether Hermes sends the booking key's placeholder to MCP servers; #14417 tracks the live check.
Beyond CI
Each relative link and anchor in the changed files resolves to an existing file and heading.