Repository navigation
docs: prepare the v0.6.0 release - #435
Merged
Merged
Conversation
Add the 0.6.0 changelog entry covering the commits since v0.5.0. Pin the admission-policy samples and the verification examples to v0.6.0, as RELEASE.md step 3 requires before tagging. Nothing in CI rewrites those strings, and v0.3.0 shipped with them stale. Correct the existing Unreleased entry to cite #412, the pull request that renamed the NCCL gauges, rather than #408, the issue it closed. Every other entry in the file cites the pull request. Flip ADR-082 and ADR-084 to Accepted. Both describe behaviour that has landed: the ResourceSlice architecture fallback in #379 and the read-only MCP server in #372. ADR-086 stays Proposed because only half of it shipped: Certification and Workflow moved to the cache collector in #414, but Job status is still write-driven and the timeout write is not yet exclusive. Signed-off-by: Ebot Ndip-Agbor <endipagbor@nvidia.com>
lalitadithya
approved these changes
Oct 5, 2026
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 🧰 Additional context used📚 Code guidelines (1)No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (7)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe changelog adds the 0.6.0 release entry and its release URL. Release-verification examples and sample policy identity pins now use the v0.6.0 tag instead of v0.5.0. Two ADRs now have Accepted status. Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Other Merge Risk: ⚪ Minimal · up to These release-preparation changes present no identified merge-blocking risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Contributor
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.
Summary
Prepares the tree for
v0.6.0. No behaviour changes; this is the pre-tag stepRELEASE.md
requires before the tag is pushed.
The 0.6.0 changelog entry.
[Unreleased]held one line against 25 merged commits.Every entry below is checked against the code rather than the pull request body: the
leader-gated cache collector at
pkg/controller/metrics_status.go:75,113, the four MCPtools at
pkg/mcpserver/server.go:104-125,MinWaitTimeout = time.Second,schedulerNameKAIon both render paths, and thertxpro6000eight-GPU default atpkg/catalog/entries/_lib/gpu-defaults.yaml:47.The admission-policy pins.
config/samples/policy/*.yamlstill namedrefs/tags/v0.5.0. Nothing in CI rewrites them —test/docspolicychecks the identityprefix, not the tag — so a sample copied at
v0.6.0would verify against the previousrelease's signing identity. That is the stale-pin outage RELEASE.md step 3 exists to
prevent, and
v0.3.0shipped with it. The verification examples indocs/operations/verifying-artifacts.mdandRELEASE.mdmove for the same reason.ADR-082 and ADR-084 to Accepted. Both describe behaviour that has landed: the
ResourceSlice architecture fallback (#379,
pkg/controller/gpu_resourceslice_detect.go)and the read-only MCP server (#372,
pkg/mcpserver/). ADR-086 staysProposedonpurpose. Only half of it shipped — Certification and Workflow moved to the cache
collector in #414, but
nvcre_job_statusis still write-driven(
pkg/controller/metrics_status.go:41) and the timeout write atpkg/controller/workflow_controller.go:1434is still a baremeta.SetStatusConditionrather than the exclusive set decision B specifies.
One citation fix. The existing NCCL-gauge entry cited #408, the issue. Every other
entry in the file cites the pull request, which is #412.
Version
v0.6.0, not a patch. Four features landed: the MCP server (#372), architectureresolution without the
nvidia.com/gpu.productlabel (#379), the GCP RTX PRO 6000overlays (#396), and the Certification and Workflow status gauges (#414).
Nothing is breaking. #402's presence rules only forbid add-after-create and
remove-after-create on fields that already carried
self == oldSelf, so no storedobject is invalidated. #413's
labelsdefault reproduces therelease: prometheusthetemplate previously hardcoded.
honorLabels: truedoes change series labels on upgrade,which is why it has its own Changed entry and an opt-out.
Testing
go test ./test/releasepolicy/ ./test/docspolicy/passes on this branch.Related Issue
Closes N/A — release preparation.
Type of Change