[kristinapathak]

TL;DR

Ports the chart release branch check from #2974 to the compute-plane 1.0 train. A patch on this train can pin a helm-nvca-operator version released after the train split from main. The stack inventory now accepts that chart tag when origin/main or the chart's maintenance branch contains it, so the patch still gets its inventory.

Additional Details

Why:

• The stack inventory renders the pinned helm-nvca-operator chart from its release tag, deploy/helm/nvca-operator/vX.Y.Z. It only accepts a tag that is an ancestor of the stack commit, the trust boundary from fix(release): generate self-managed stack inventory #1779.
• v1.0.0 and v1.0.2 through v1.0.4 all pin chart 1.28.0, which is in this branch's history, and each published its inventory. A patch that moves the pin to a later chart, from main or from a release-deploy/helm/nvca-operator/v1.X branch, would fail the inventory and publish without it. See ci(release): stack branch-cut opens a conflicting VERSION PR and the first train release has no inventory #2970 and ci(release): stack inventory rejects a patch that pins a chart released after the branch cut #2972.
• The tag workflow runs tools/docs-version-sync from the tagged commit, so the fix on main does not reach tags on this branch.

What changed:

• If a pinned chart tag is not an ancestor of the stack commit, docs-version-sync accepts it when origin/main or origin/release-<tag prefix>X.Y for the tag's minor contains it. It logs that branch to stderr. chartReleaseBranchContaining is the same code as on main.
• Any other tag still fails: a tag on an unmerged branch, on another chart's maintenance branch, or on the wrong minor's branch.

Not ported:

• The release snapshot lineage from fix(release): open stack trains with a mergeable bump and an inventory #2971 and fix(release): accept source charts from the 1.1 train snapshot source #2973. This branch has no snapshot commit. It continues main's history, so chart tags released on main before the split are already ancestors of its stack commits. A new test case covers that.
• The docs change from fix(release): render stack inventories that pin a chart released after the cut #2974. docs/dev/github-release-process.md on this branch predates the sections it edits.

This changes nothing under deploy/stacks/nvcf-compute-plane, so merging it does not cut a new stack patch. Not customer visible. No dependency changes.

For the Reviewer

• tools/docs-version-sync/resolved_inventory_publish.go: the ancestry check now falls back to chartReleaseBranchContaining.
• The new test mirrors the one from fix(release): render stack inventories that pin a chart released after the cut #2974, with the stack on a maintenance branch that continues main instead of a snapshot.

For QA

• go test ./... in tools/docs-version-sync: pass.
• python3 tools/ci/test-github-release.py: pass (98 tests).
• go vet ./..., gofmt -l, and git diff --check: clean.
• Ran the inventory's source chart step against the real deploy/stacks/nvcf-compute-plane/v1.0.4 tag (stack commit aae64c9a1):
  • With the tag's own pin (helm-nvca-operator 1.28.0): pass, from the stack's own history.
  • With the pin moved to 1.29.6, released on main after the split: pass with this change (using the release from origin/main). Before it, it fails with is not an ancestor of stack commit.
• No release-deploy/helm/nvca-operator/v1.X branch exists yet, so the unit test covers the maintenance branch case.
• The full inventory render was not run locally. It pulls the stack's other charts from the release chart registry, which only the release workflow can reach.
• QA needed: no. Release tooling only.

Issues

Relates to #2970
Relates to #2972

Checklist

• I am familiar with the Contributing Guidelines.
• I have signed off my commits for Developer Certificate of Origin (DCO) compliance.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review: 1

• main

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: NVIDIA/nvcf
• Branch: kristinapathak/cp-v1.0-inventory-fixes
• File: .coderabbit.yaml
• Commit: 18e5d8f
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Enterprise
• Run ID: f34e6740-99d0-4556-a0f4-cbd87a644a0e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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