From e31a60add1416ef7e95949bbd44013804c643f87 Mon Sep 17 00:00:00 2001 From: Herbert Damker <52109189+hdamker@users.noreply.github.com> Date: Thu, 9 Jul 2026 19:14:04 +0200 Subject: [PATCH 1/2] docs(release-automation): tie the RM-review start to the readiness checkbox The Codeowner Actions note said review starts "when all three boxes are ticked", but the deferred-warnings box is optional for alpha releases, so that misfires. Point the note at the explicit "ready for Release Management review" box instead. --- .../templates/pr_bodies/release_review_pr.mustache | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/release_automation/templates/pr_bodies/release_review_pr.mustache b/release_automation/templates/pr_bodies/release_review_pr.mustache index 9d5daa1f..28ffa9dd 100644 --- a/release_automation/templates/pr_bodies/release_review_pr.mustache +++ b/release_automation/templates/pr_bodies/release_review_pr.mustache @@ -16,7 +16,7 @@ Edit and review this PR before merging it into the release snapshot. After Codeo ### Codeowner Actions -_Tick each box once done. Release Management review starts when all three boxes are ticked._ +_Tick each box once done. Ticking the last box — "The release is ready for Release Management review" — starts the Release Management review._ - [ ] **Update the CHANGELOG** From 1d1814229d577f0b4ce6b01748f4dcb4f0108dbb Mon Sep 17 00:00:00 2001 From: Herbert Damker <52109189+hdamker@users.noreply.github.com> Date: Fri, 10 Jul 2026 10:10:45 +0200 Subject: [PATCH 2/2] feat(release-automation): add an RM reviewer-assignment action to the Review PR template MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Add a first Release Management Actions checkbox — "Assign the Release Management reviewer(s) as assignee(s) of this PR" — plus an intro line scoping the whole section to Release Management reviewers, so codeowners do not take these boxes as their own. The PR assignee is the concrete reviewer the Release Progress Tracker's Review Queue surfaces, so making the assignment an explicit review step keeps that queue populated. --- .../templates/pr_bodies/release_review_pr.mustache | 3 +++ release_automation/tests/test_template_loader.py | 2 ++ 2 files changed, 5 insertions(+) diff --git a/release_automation/templates/pr_bodies/release_review_pr.mustache b/release_automation/templates/pr_bodies/release_review_pr.mustache index 28ffa9dd..029f9786 100644 --- a/release_automation/templates/pr_bodies/release_review_pr.mustache +++ b/release_automation/templates/pr_bodies/release_review_pr.mustache @@ -45,6 +45,9 @@ _Tick each box once done. Ticking the last box — "The release is ready for Rel ### Release Management Actions +_The following actions and checks are done by a Release Management reviewer before approving the PR:_ + +- [ ] **Assign the Release Management reviewer(s) as assignee(s) of this PR** - [ ] CHANGELOG follows the release documentation rules - [ ] Breaking changes are documented and version updates follow SemVer rules - [ ] Mandatory release assets are present for each API according to its status diff --git a/release_automation/tests/test_template_loader.py b/release_automation/tests/test_template_loader.py index 503437df..f3b322cc 100644 --- a/release_automation/tests/test_template_loader.py +++ b/release_automation/tests/test_template_loader.py @@ -47,6 +47,8 @@ def test_render_release_review_pr_template(self): assert "Commonalities r3.4" in result assert "Mandatory release assets are present for each API according to its status" in result assert "All remaining validation warnings are documented in issues and the reasons for deferral are defensible" in result + assert "Assign the Release Management reviewer(s) as assignee(s) of this PR" in result + assert "The following actions and checks are done by a Release Management reviewer before approving the PR" in result assert "### Valid next actions for codeowners" in result assert "Snapshot: [`r4.1-abc1234`]" in result assert "
" in result