chore: bump version to 1.6.0 post 1.5.0 branch cut

[pvijayakrish]

Bump version to 1.6.0 post 1.5.0 branch cut.

Summary by CodeRabbit

• Release
  • Updated the platform and related packages to version 1.6.0.
  • Aligned local package dependencies and Python package metadata with the 1.6.0 release.
  • Updated Helm chart and application versions to 1.6.0.
• Documentation
  • Updated Helm chart documentation and dependency references to reflect version 1.6.0.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 535bd2b1-8981-4d11-b197-db274bcb1773

📥 Commits

Reviewing files that changed from the base of the PR and between 6744faa and ee1da73.

⛔ Files ignored due to path filters (4)

• Cargo.lock is excluded by !**/*.lock
• lib/bindings/kvbm/Cargo.lock is excluded by !**/*.lock
• lib/bindings/python/Cargo.lock is excluded by !**/*.lock
• lib/runtime/examples/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (15)

• Cargo.toml
• deploy/helm/charts/platform/Chart.yaml
• deploy/helm/charts/platform/README.md
• deploy/helm/charts/platform/components/operator/Chart.yaml
• lib/bindings/kvbm/Cargo.toml
• lib/bindings/kvbm/pyproject.toml
• lib/bindings/python/Cargo.toml
• lib/bindings/python/pyproject.toml
• lib/kvbm-common/Cargo.toml
• lib/kvbm-engine/Cargo.toml
• lib/kvbm-kernels/Cargo.toml
• lib/kvbm-logical/Cargo.toml
• lib/kvbm-physical/Cargo.toml
• lib/runtime/examples/Cargo.toml
• pyproject.toml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

Walkthrough

The release metadata was updated from 1.5.0 to 1.6.0 across workspace manifests, Rust and Python packages, Helm charts, and related documentation.

Changes

Version release metadata

Layer / File(s)	Summary
Workspace version and dependencies Cargo.toml	The workspace version and local workspace dependency requirements were updated to 1.6.0.
Package manifest versions lib/*/Cargo.toml, lib/*/pyproject.toml, pyproject.toml	Rust and Python package versions were updated to 1.6.0. The ai-dynamo-runtime dependency was also aligned to 1.6.0.
Helm chart release metadata deploy/helm/charts/platform/*	Platform and operator Helm chart versions, dependency versions, and documented versions were updated to 1.6.0.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to ee1da

No concrete release-metadata inconsistency or other merge-blocking risk is identified.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description states the main purpose of the pull request, but it omits the required Overview, Details, reviewer-start guidance, and Related Issues sections. It also does not confirm whether the pul…	Add all required template sections. Include change details, identify files for reviewer focus, and either link the related issue or check the confirmation that no related issue exists.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly states that the project version was bumped to 1.6.0 after the 1.5.0 branch cut. It accurately summarizes the main change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

Full details: Description check

Explanation

The description states the main purpose of the pull request, but it omits the required Overview, Details, reviewer-start guidance, and Related Issues sections. It also does not confirm whether the pull request has a related issue.

• Fix all pre-merge checks with AI

---

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

[dmitry-tokarev-nv]

Version bump: completeness and correctness check

I checked the set of files, not the diff text. Every one of the 109 changed lines is a version declaration. Nothing historical and no pin to a published artifact was rewritten. All four Cargo workspaces pass --locked. The chart README matches what helm-docs produces. One P3 on the pull request description.

[P3] The description has no tracker ID and no Summary or Validation section. AGENTS.md asks for both, and the equivalent bump before this one carried a bare ID. Please add the ID and the two sections.

Old-version sweep: every remaining 1.5.0, classified

I compared the file set against the previous post-cut bump (c13fdcec64, 1.4.0 to 1.5.0). The two sets are identical except for deploy/helm/charts/snapshot/Chart.yaml, which no longer exists in the tree.

Defects found: none.

Intentional keeps:

Where	Why it must stay
recipes/**/deploy.yaml, docs/fern/pages/**, examples/deployments/**	Pins to published 1.5.0 images. A bump makes them unpullable.
container/context.yaml:34	Default EPP_IMAGE, a published image. The comment above it states CI overrides it per commit.
deploy/helm/charts/power-agent/Chart.yaml	Own version line, 1.3.1 / 1.2.0. Never on the 1.5.0 train.
lib/gpu_memory_service/pyproject.toml (0.9.0), benchmarks/pyproject.toml (0.1.0), lib/bindings/python/codegen/Cargo.toml (0.1.0)	Own version lines. cargo metadata reports dynamo-codegen as the only workspace member that is not 1.6.0.
deploy/operator/**, container/compliance/**, docs/fern/components/releases.data.ts	Test fixtures, doc comments about past behavior, third-party package versions, release history.
lib/kvbm-logical/Cargo.toml:39 (proptest = "1.5.0")	Third-party crate.

deploy/helm/charts/platform/Chart.yaml has no appVersion. That is by design, not a miss: .github/scripts/prepare_nightly_helm.py:83 says "platform has no appVersion".

Lockfiles: --locked in all four workspaces, with a control

CARGO_TARGET_DIR=/tmp/claude/pr15009/target cargo metadata --locked
.                      OK
lib/bindings/python    OK
lib/bindings/kvbm      OK
lib/runtime/examples   OK

Control: I set one version = "1.6.0" line in the root Cargo.lock back to 1.5.0. --locked then failed. The pass above is real.

Internal dependencies: cargo metadata --locked --no-deps resolves every path dependency against its version = "1.6.0" requirement. It reports two versions across all members, 1.6.0 and 0.1.0, and 0.1.0 is dynamo-codegen alone. No crate requires a version that the workspace does not hold.

The lockfile diff contains no line other than version = "1.5.0" to version = "1.6.0".

Helm chart: both fields, and the README matches its generator

deploy/helm/charts/platform/components/operator/Chart.yaml moves version and appVersion together, lines 30 and 37. deploy/helm/charts/platform/Chart.yaml moves version and the dynamo-operator dependency pin, lines 22 and 28.

I ran make generate-helm-docs in the chart directory of a separate worktree. helm-docs 1.14.2 produced a byte-identical README.md, so git status stayed empty.

Control: I edited the operator row of the README back to 1.5.0 and reran the generator. It restored 1.6.0, so the gate does detect a stale README.

CI covers this. deploy/operator/Makefile:215 runs generate-helm-docs against ../helm/charts/platform and fails on a dirty tree. .github/actions/check-deploy-component/action.yml runs make check in deploy/operator, and .github/workflows/pre-merge.yml:375 calls that action.

Python packages, and the unpublished 1.6.0 question

pyproject.toml moves ai-dynamo to 1.6.0 and its ai-dynamo-runtime== pin with it. lib/bindings/python/pyproject.toml and lib/bindings/kvbm/pyproject.toml move too. No Python module holds a literal version: they all read it from package metadata.

The ai-dynamo-runtime==1.6.0 pin resolves from a wheel built in the same tree by container/templates/wheel_builder.Dockerfile:574, not from an index. It is satisfiable today.

The operator image tag is the one thing that now names an unpublished artifact. deployment.yaml:70 falls back to .Chart.AppVersion, so a plain helm install from this tree asks for kubernetes-operator:1.6.0, which cannot exist until the first 1.6.0 publish. I am not raising this as a finding: values.yaml:83 already documents the state ("only exists for GA releases"), .github/scripts/prepare_nightly_helm.py rewrites these versions for every nightly publish, and the previous bump c13fdcec64 moved appVersion the same way at the same point in the cycle. This pull request does not introduce or worsen it.

[dmitry-tokarev-nv]

Re-approved at da7ab5768.

The branch merged main. The commit I read before, ee1da739, is still an ancestor of the head, so this is a merge, not a force-push. The merge base moved from 6744faa5 to 6be0ab24, which brought in 11 commits from main. The version bump itself did not move: the pull-request diff taken at the old merge base and the diff taken at the new merge base are the same patch. Nothing that arrived from main carries the old version, and nothing that must stay pinned was bumped. No findings.

Diff-of-diffs, lock check and old-version sweep

Merge bases, and the incoming commits between them:

old base 6744faa5284de95351994aebc4f2de6323ea7062
new base 6be0ab241d8d02717e06cdada3c4eb7ba5911031
git rev-list --count old..new  ->  11

Diff of diffs, old base against old head versus new base against new head:

git diff 6744faa5...ee1da739 > old.diff   # 935 lines
git diff 6be0ab24...da7ab576 > new.diff   # 935 lines
diff old.diff new.diff
915c915
< index ee0647c633..8e2355f820 100644
> index 02aca2a733..c4c7b57611 100644

The only difference is the blob index line for pyproject.toml, because a commit from main also edited that file. The added and removed lines are identical.

The whole patch is one substitution, in both directions:

removed lines that do not contain 1.5.0: 0
added   lines that do not contain 1.6.0: 0
109 removed, 109 added

Every locally built package in all four lock files is at 1.6.0. The one exception is dynamo-codegen at 0.1.0, which is a build helper and was never on the release train. All four lock files agree with their manifests:

cargo metadata --locked --offline --no-deps     -> exit 0   (workspace root)
lib/bindings/python   -> exit 0
lib/bindings/kvbm     -> exit 0
lib/runtime/examples  -> exit 0

No file added by the 11 incoming commits carries the old version, and no line they added carries it:

git diff old..new | grep '^+' | grep 1.5.0   ->  no output

Old-version references that are correct to leave:

Place	Why it stays
deploy/operator/internal/features/runtime/gates.go and its tests	compatibility floor: the first runtime that has the feature
deploy/operator/api/... and config/crd/bases/...	the same floor, in the generated CRD text
deploy/helm/charts/power-agent/Chart.yaml (1.3.1)	independent chart version, also untouched by the 1.4.0 to 1.5.0 bump
container/context.yaml epp_image: ...dynamo-epp:1.5.0	pin to a published image; a 1.6.0 tag does not exist yet, and CI overrides it
recipes/, examples/, docs/ image tags	published or dev image tags, not the source version
docs/fern/components/releases.data.ts	release history
container/compliance/tests/test_cargo_sbom.py	synthetic fixture; it never reads the workspace version
proptest = "1.5.0", google-crc32c>=1.5.0, xstrings v1.5.0	third-party versions

The 1.4.0 to 1.5.0 bump, commit c13fdcec64, set the same boundary. recipes/, examples/ and docs/ held 33 files with 1.4.0 both before and after it.

Generated files in this change: the four Cargo.lock files, checked above, and deploy/helm/charts/platform/README.md, which helm-docs produces. I could not run helm-docs on this machine, so I compared the two changed README lines against Chart.yaml by hand. The version badge and the dynamo-operator row both read 1.6.0 and match Chart.yaml. I found no job that regenerates the README and fails on a difference.