From 8131ff9eaf7d350d561f15948000ac572839e2c0 Mon Sep 17 00:00:00 2001 From: Yuchao Yan Date: Fri, 11 Sep 2026 03:25:44 +0000 Subject: [PATCH 1/4] Update Python release skill guidance --- .../SKILL.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/.github/skills/http-client-python-bump-and-release/SKILL.md b/.github/skills/http-client-python-bump-and-release/SKILL.md index d380839446b..9efe2999cbe 100644 --- a/.github/skills/http-client-python-bump-and-release/SKILL.md +++ b/.github/skills/http-client-python-bump-and-release/SKILL.md @@ -70,6 +70,19 @@ npm install -g npm-check-updates npm run change:version ``` + Verify that the script updated both the emitter version in `package.json` and `CHANGELOG.md`. If neither file was updated: + - Increment the third component of the emitter version in `package.json` (for example, `a.b.c` to `a.b.(c+1)`). + - Add this entry near the top of `CHANGELOG.md`, immediately after the changelog title: + + ```markdown + ## + + ### Bump dependencies + + - Bump dependencies of `@typespec/*` and `@azure-tools/*` to latest versions + ``` + - Verify that the version in `package.json` matches the new `CHANGELOG.md` heading. + 8. Build and commit: ```bash @@ -84,3 +97,16 @@ npm install -g npm-check-updates ``` 10. Create PR with title `[python] release new version` and no description. + +## Post-Process Review + +1. After the pull request is created, review the complete release run: commands executed, command output, manual interventions, validation results, changed files, commit, push, cleanup, and PR creation. +2. Update this skill only when the completed run provides a concrete finding and a strong reason for the change, such as: + - A documented step failed or produced an incorrect result. + - The agent needed an undocumented manual correction to complete the release. + - A step was ambiguous enough to create a real risk or delay. + - A command was unnecessary or could be replaced by a demonstrably safer or more reliable command. +3. Do not change the skill based on preference, speculation, or an unobserved edge case. For every update, record the observed evidence and explain why the edit improves future releases. +4. Keep any skill update minimal, validate its formatting and frontmatter, and keep it separate from the completed release PR unless the user explicitly asks to include it there. +5. If the review finds no evidence-backed improvement, leave the skill unchanged and state that no update was warranted. +6. Return the branch name, released package version, `@typespec/http-client-python` version, commit hash, pull request URL, review findings, and any skill update to the user. From 3c0d1185e2b1028906227ddea6be7c5aa2c8a675 Mon Sep 17 00:00:00 2001 From: Yuchao Yan Date: Fri, 11 Sep 2026 11:56:20 +0800 Subject: [PATCH 2/4] Update verification instructions for version script Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- .github/skills/http-client-python-bump-and-release/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/skills/http-client-python-bump-and-release/SKILL.md b/.github/skills/http-client-python-bump-and-release/SKILL.md index 9efe2999cbe..3c375ab9188 100644 --- a/.github/skills/http-client-python-bump-and-release/SKILL.md +++ b/.github/skills/http-client-python-bump-and-release/SKILL.md @@ -70,7 +70,7 @@ npm install -g npm-check-updates npm run change:version ``` - Verify that the script updated both the emitter version in `package.json` and `CHANGELOG.md`. If neither file was updated: + Verify that the script updated both the emitter version in `package.json` and `CHANGELOG.md`. If either file was not updated: - Increment the third component of the emitter version in `package.json` (for example, `a.b.c` to `a.b.(c+1)`). - Add this entry near the top of `CHANGELOG.md`, immediately after the changelog title: From 6256457e80a3b46fd0d1ba97b89754cccff0d4af Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 11 Sep 2026 04:01:44 +0000 Subject: [PATCH 3/4] style: format Python release skill Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com> --- .github/skills/http-client-python-bump-and-release/SKILL.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/skills/http-client-python-bump-and-release/SKILL.md b/.github/skills/http-client-python-bump-and-release/SKILL.md index 3c375ab9188..014917d0d19 100644 --- a/.github/skills/http-client-python-bump-and-release/SKILL.md +++ b/.github/skills/http-client-python-bump-and-release/SKILL.md @@ -81,7 +81,8 @@ npm install -g npm-check-updates - Bump dependencies of `@typespec/*` and `@azure-tools/*` to latest versions ``` - - Verify that the version in `package.json` matches the new `CHANGELOG.md` heading. + + - Verify that the version in `package.json` matches the new `CHANGELOG.md` heading. 8. Build and commit: From 340f9e761e59ab89519ed1d4a602558d99de0ffd Mon Sep 17 00:00:00 2001 From: Yuchao Yan Date: Fri, 11 Sep 2026 12:44:04 +0800 Subject: [PATCH 4/4] Update verification instructions for version changes Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --- .github/skills/http-client-python-bump-and-release/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/skills/http-client-python-bump-and-release/SKILL.md b/.github/skills/http-client-python-bump-and-release/SKILL.md index 014917d0d19..1026d0c6bb5 100644 --- a/.github/skills/http-client-python-bump-and-release/SKILL.md +++ b/.github/skills/http-client-python-bump-and-release/SKILL.md @@ -70,7 +70,7 @@ npm install -g npm-check-updates npm run change:version ``` - Verify that the script updated both the emitter version in `package.json` and `CHANGELOG.md`. If either file was not updated: + Verify that the script updated both the emitter version in `package.json` and `CHANGELOG.md`. If neither file was updated: - Increment the third component of the emitter version in `package.json` (for example, `a.b.c` to `a.b.(c+1)`). - Add this entry near the top of `CHANGELOG.md`, immediately after the changelog title: