Repository navigation
chore: set version 1.3.1 on release/1.3.1 - #12144
Merged
Merged
Conversation
Stamp the workspace version 1.3.0 -> 1.3.1 across pyproject/Cargo/Helm and sync Cargo.lock, so the on-demand release job's bump step is a no-op on this branch instead of pushing an unreviewed version commit onto release/1.3.1. Generated with .github/scripts/apply_dev_version.py --set-version 1.3.1 --containers all --helm all, plus cargo update --workspace. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Nate Mailhot <nmailhot@nvidia.com>
Follow the manual bump pattern in f0c4516 (#12040), which touches sites the script does not: - lib/runtime/examples: nested workspace, intentionally skipped by the script - lib/kvbm-consolidator: was pinned at a stale 1.2.0; switched to version.workspace = true, the same fix f0c4516 applied on main - deploy/helm/charts/platform/README.md: helm-docs badge, dependency table, and the operator image.tag row (concrete here, empty on main) - lib/bindings/python, lib/bindings/kvbm, lib/runtime/examples Cargo.lock: separate lockfiles, not reached by a root cargo update --workspace docs/reference/support-matrix.md is deliberately excluded: its version label describes main/ToT (now 1.4.0), not this branch — release/1.3.0 likewise left it at 1.3.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Nate Mailhot <nmailhot@nvidia.com>
github-actions
Bot
added
chore
documentation
Contributor
![dynamo-review-agent[bot]](https://avatars.githubusercontent.com/u/201626793?s=60&v=4){kind=small}
Drop the shields.io badge bump from the version PR; keep the plain-text version sites (operator dependency row, image.tag row). The badge is a generated img.shields.io URL, not a version pin. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Nate Mailhot <nmailhot@nvidia.com>
dagil-nvidia
approved these changes
Jul 25, 2026
2 tasks
dagil-nvidia
added a commit
that referenced
this pull request
Aug 4, 2026
The 'operator' CI job runs helm-docs over deploy/helm/charts/platform and then asserts the git tree is clean. It has been failing on release/1.3.1 since the version bump merged: ERROR: Git tree is dirty after running validation steps. - + make: *** [Makefile:199: check] Error 1 #12144 updated two version rows in that README by hand (the subchart table and the operator image.tag row) but missed the helm-docs badge on line 22, so every CI run regenerates it and finds a diff. This is the only 1.3.0 reference left in the file. It is also the sole reason the pre-merge-status-check and deploy-status-check rollups are red -- their job matrices report success or skipped for everything except 'operator'. 'operator' passes on release/1.3.0 and on main; the failure is specific to release/1.3.1 and dates to the exact minute #12144 merged. Signed-off-by: Dan Gil <dagil@nvidia.com>
nv-nmailhot
added a commit
that referenced
this pull request
Aug 4, 2026
TEMPORARY redirect of the push-flow fallbacks from 1.4.0/rc3 to 1.3.1/rc1 to stage a patch-line RC off the existing release/1.3.1 branch. release/1.3.1 is already stamped 1.3.1 (#12144), so the bump step is a no-op there. Reverted immediately after the run launches so the branch returns to its 1.4.0 rc3 configuration. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Signed-off-by: Nate Mailhot <nmailhot@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
2 participants
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.
Overview:
Details:
Where should the reviewer start?
Related Issues
🔗 This PR is linked to an issue:
🚫 This PR is NOT linked to an issue: