Cherry-pick PRs to a Release Branch

Cherry-pick all merged main PRs labeled cherry-pick-<version> (but not cherry-pick-done) into the corresponding release/<version> branch, one by one in merge order.

Step 1 — Identify the target version

Ask the user for the release version (e.g. 0.44.0) and target release candidate (e.g. rc2) if not already provided. Confirm whether this is the final RC.

Set VERSION=<version> for use in subsequent steps.

Step 2 — Audit candidates for missing labels

Before fetching the labeled queue, audit for missing bug fixes:

• Non-final RC: audit release NVBugs and recent merged PRs.
• Final RC: audit only fixes tied to NVBugs with the exact keyword Committed_ModelOpt_<VERSION> and QA-verification evidence for the fix. Verify that evidence in the NVBug or linked QA results before recommending Needs label; if missing or unclear, classify as Unknown and ask for confirmation. Skip the general recent-PR audit; do not introduce general bug-fix PRs or fixes tied only to NVBugs committed for another release.

Audit release NVBugs