Skip to content

ci: pin FW-CI-templates to NVIDIA-NeMo/FW-CI-templates#480 (mirror branch protection)#527

Draft
ko3n1g wants to merge 2 commits into
mainfrom
ko3n1g/ci/pin-fw-ci-pr-480
Draft

ci: pin FW-CI-templates to NVIDIA-NeMo/FW-CI-templates#480 (mirror branch protection)#527
ko3n1g wants to merge 2 commits into
mainfrom
ko3n1g/ci/pin-fw-ci-pr-480

Conversation

@ko3n1g
Copy link
Copy Markdown
Contributor

@ko3n1g ko3n1g commented May 22, 2026

Claude summary

Companion to NVIDIA-NeMo/FW-CI-templates#480, which mirrors the branch-protection rule of [rv][0-9].[0-9].[0-9] onto deploy-release/* so the validate-only release rehearsal is gated by the same required status checks as a real release.

Change

Bumps the FW-CI-templates pin in release.yaml to commit 042e967e4ac9652c324cbd5b78fd126c089aec6c (the head of ko3n1g/feat/mirror-release-branch-protection on FW-CI-templates).

What's being validated

After merge of FW-CI-templates#480, a workflow-dispatch of release.yaml with dry-run: true should:

  1. Run the new "Mirror branch protection" step in bump-next-version.
  2. Update the deploy-release/* rule on this repo to match [rv][0-9].[0-9].[0-9].
  3. Open the bump PR with Nemo_CICD_Test (or the repo's equivalent) shown as a required check.
  4. Block merge of the bump until the required checks pass.

Prerequisites

The nemo-automation-bot GitHub App must hold administration: write at the org installation, otherwise the mirror step fails the bump.

Rollout

This PR is draft + do not merge — pinned to an unmerged SHA. Once FW-CI-templates#480 lands and ships in a new tag, re-pin to that tag and merge.

@ko3n1g ko3n1g force-pushed the ko3n1g/ci/pin-fw-ci-pr-480 branch from 0f4ed68 to 9d61c4e Compare May 22, 2026 11:56
@ko3n1g ko3n1g force-pushed the ko3n1g/ci/pin-fw-ci-pr-480 branch from 9d61c4e to 5f3b387 Compare May 22, 2026 12:05
@ko3n1g ko3n1g force-pushed the ko3n1g/ci/pin-fw-ci-pr-480 branch from 5f3b387 to a691b68 Compare May 22, 2026 12:11
@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented May 22, 2026

/ok to test a691b68

@ko3n1g ko3n1g force-pushed the ko3n1g/ci/pin-fw-ci-pr-480 branch from a691b68 to a1204fc Compare May 22, 2026 12:27
@ko3n1g ko3n1g force-pushed the ko3n1g/ci/pin-fw-ci-pr-480 branch from a1204fc to db53631 Compare May 22, 2026 12:28
@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented May 22, 2026

/ok to test db53631

@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented May 22, 2026

/ok to test 6efd2ee

@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented May 22, 2026

/ok to test 62ca38c

@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented May 22, 2026

/ok to test fe9d50b

@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented May 22, 2026

/ok to test fe9d50b

1 similar comment
@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented May 22, 2026

/ok to test fe9d50b

@ko3n1g ko3n1g force-pushed the ko3n1g/ci/pin-fw-ci-pr-480 branch from fe9d50b to bf5344e Compare May 22, 2026 13:35
@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented May 22, 2026

/ok to test bf5344e

…anch protection)

Companion PR to NVIDIA-NeMo/FW-CI-templates#480, which mirrors the
branch-protection rule of `[rv][0-9].[0-9].[0-9]` onto `deploy-release/*` so
the validate-only release rehearsal is gated by the same required status
checks as a real release.

Pinned to commit f680963ed397a4ff0cd4c983a3a3071c209e5e77 on `ko3n1g/feat/mirror-release-branch-protection`.
Re-pin to a released tag once FW-CI-templates#480 lands.

Signed-off-by: oliver könig <okoenig@nvidia.com>
@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented May 22, 2026

/ok to test 5de6b81

Signed-off-by: oliver könig <okoenig@nvidia.com>
@ko3n1g
Copy link
Copy Markdown
Contributor Author

ko3n1g commented May 22, 2026

/ok to test b701872

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant