From 099abc562541b373ed6f99041e5eed169662ac44 Mon Sep 17 00:00:00 2001 From: eavanvalkenburg Date: Thu, 12 Nov 2026 17:08:18 +0100 Subject: [PATCH] Python: Match release titles to tag names --- python/.github/skills/agent-framework-py-release/SKILL.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/python/.github/skills/agent-framework-py-release/SKILL.md b/python/.github/skills/agent-framework-py-release/SKILL.md index 7d84af24727..2452a4dcb39 100644 --- a/python/.github/skills/agent-framework-py-release/SKILL.md +++ b/python/.github/skills/agent-framework-py-release/SKILL.md @@ -478,8 +478,9 @@ The push output includes a `Create a pull request for '' on GitHub by vi ### 10. Maintainer handoff: tag and existing draft (only when authorized) After the reviewed bump PR merges, the maintainer selects the exact merged commit and creates the **one** overall -tag matching its `python/.github/release-.json`. The maintainer creates a GitHub **draft** release for that tag, with the -human-written title, complete release notes, and intended prerelease flag. Do not use a published release as the +tag matching its `python/.github/release-.json`. The maintainer creates a GitHub **draft** release for that tag. +The release title must exactly match the full tag name, including the `python-` prefix (for example, `python-1.26.0`). +Include complete release notes and the intended prerelease flag. Do not use a published release as the trigger and do not create per-package tags. Release notes must be complete **before ESRP approval**; do not edit the draft, tag, or selected source while a release run is in progress.