[kristinapathak]

TL;DR

Backport of #2974 to the self-managed 1.1 train. A patch on this train can pin a source chart version released after the train was cut. 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 each pinned source chart from its release tag. It only accepts a tag from reviewed source, the trust boundary from fix(release): generate self-managed stack inventory #1779.
• fix(release): accept source charts from the 1.1 train snapshot source #2973 already lets this branch accept chart tags from the default-branch commit that the v1.1 snapshot copies. A later patch can move a pin to a chart released after the cut, from main or from a chart maintenance branch such as release-deploy/helm/http-invocation/v1.6. That tag is outside both histories, so the inventory fails. See 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 outside the stack commit's history and its snapshot source, 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.
• Any other tag still fails: a tag on an unmerged branch, on another chart's maintenance branch, or on the wrong minor's branch.
• tools/docs-version-sync now matches main exactly.
• docs/dev/github-release-process.md gets the two paragraphs from fix(release): render stack inventories that pin a chart released after the cut #2974. The Snapshot-Of paragraph next to the second one came from fix(release): open stack trains with a mergeable bump and an inventory #2971 and is not on this branch, so it is not added here.

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

For the Reviewer

• Cherry-pick of the squash commit of fix(release): render stack inventories that pin a chart released after the cut #2974. The only conflict was in the docs file.
• git diff origin/main -- tools/docs-version-sync is empty on this branch.

For QA

• go test ./... in tools/docs-version-sync: pass.
• python3 tools/ci/test-github-release.py: pass (118 tests).
• git diff --check: clean.
• Ran the inventory's source chart step against the real deploy/stacks/self-managed/v1.1.0 tag (stack commit ad30a54ef):
  • With the tag's own pins (invocation 1.9.0, rate limiter 1.3.0, NATS auth callout 1.4.2): pass.
  • With invocation pinned to 1.6.2, which exists only on release-deploy/helm/http-invocation/v1.6: pass with this change (using the release from origin/release-deploy/helm/http-invocation/v1.6). Before it, it fails with is not an ancestor of stack commit ... or of its release snapshot source ....
• 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 #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/v1.1-maintenance-pins
• File: .coderabbit.yaml
• Commit: 673e0a4
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 661269fb-7b87-49bf-b3c1-27d5cf4eefb5

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.}

[github-actions]

🌿 Preview your docs: https://nvidia-preview-kristinapathak-v1-1-maintenance-pins.docs.buildwithfern.com/nvcf

[balajinvda]

This PR is included in version 1.1.1.

The release is available on GitHub release.