Add prepare-release-notes and create-draft-release scripts#2556
Add prepare-release-notes and create-draft-release scripts#2556westonruter wants to merge 2 commits into
prepare-release-notes and create-draft-release scripts#2556Conversation
Assemble the release notes for the plugins currently being released — those with an open, dated milestone whose title does not contain "n.e.x.t" — by reading each plugin's stable-tag changelog entry from its readme.txt (as populated by npm run readme). Progress and warnings go to STDERR so STDOUT (the Markdown notes) can be piped to a file or the clipboard. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Create a draft GitHub release for the release date, using the combined per-plugin changelogs from `npm run prepare-release-notes` as the body. The tag and title are $RELEASE_DATE and the target is the release/$RELEASE_DATE branch. Fails early if the target branch is missing on origin or a release for the tag already exists, and authenticates the milestone lookup with the gh token to avoid rate limiting. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## trunk #2556 +/- ##
=======================================
Coverage 70.38% 70.38%
=======================================
Files 91 91
Lines 7850 7850
=======================================
Hits 5525 5525
Misses 2325 2325
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
This introduces two new scripts that help automate the release process:
npm run gather-release-notesnpm run create-draft-releaseThe former is called automatically be the later. I've updated the handbook page to explain how they are used. I used them in the most recent release.
Use of AI Tools
Changes were authored by Claude Opus 4.8 based on my prompts.