Repository navigation
Python: Match release titles to tag names - #10311
Conversation
GitHub Actions
Active
agent-framework-automation
Bot
added
documentation
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues remain for the change clarifying that Python release titles must exactly match their full tag names.
No open issues 🎉
What changed in this PR
Clarifies the Python release handoff instructions so draft release titles match the existing tag-name convention.
Changes:
- Requires titles to exactly match the full tag name, including the
python-prefix, withpython-1.26.0as an example. - Preserves release-note requirements, prerelease flags, and publication safeguards. No executable code changes.
| File | Description |
|---|---|
python/.github/skills/agent-framework-py-release/SKILL.md |
Makes exact tag/title equality explicit in the maintainer handoff instructions. |
Review effort: Balanced
GitHub Actions
Active
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
MAF Automated Review — Iteration 1
Result: No findings
Scope: full PR (1 commit(s)): 099abc562541
Model: gpt-5.6-sol
Overview
This documentation-only change makes the Python release-title convention explicit without changing the release lifecycle or automation contract. Existing guards derive validation and source selection from the immutable full tag, require exact manifest agreement, and preserve the maintainer-supplied draft metadata during finalization. No publishable defect was established.
Reviewed the supplied pull-request change set across correctness, security/reliability, architecture, and failure behavior.
No publishable findings remained after source verification for this scope.
Motivation & Context
Remove ambiguity in the Python release handoff instructions so draft release titles follow the existing tag-name convention rather than using a display title.
Description & Review Guide
python-prefix, withpython-1.26.0as an example.git diff --checkpassed; builds and unit tests were not run.Related Issue
N/A - trivial change. Clarify the existing release-title convention as requested by a maintainer following #10298.
AI Assistance
AI assistance details: GitHub Copilot assisted with the documentation wording and this PR description.
Contribution Checklist
breaking changelabel (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and the title prefix in sync automatically.