Skip to content

Add prepare-release-notes and create-draft-release scripts#2556

Open
westonruter wants to merge 2 commits into
trunkfrom
add/prepare-release-notes-script
Open

Add prepare-release-notes and create-draft-release scripts#2556
westonruter wants to merge 2 commits into
trunkfrom
add/prepare-release-notes-script

Conversation

@westonruter

Copy link
Copy Markdown
Member

This introduces two new scripts that help automate the release process:

  • npm run gather-release-notes
  • npm run create-draft-release

The 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.

westonruter and others added 2 commits June 30, 2026 18:58
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>
@westonruter westonruter added the [Type] Enhancement A suggestion for improvement of an existing feature label Jul 1, 2026
@westonruter westonruter added the skip changelog PRs that should not be mentioned in changelogs label Jul 1, 2026
@westonruter westonruter requested a review from thelovekesh as a code owner July 1, 2026 02:01
@codecov

codecov Bot commented Jul 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.38%. Comparing base (6bce616) to head (602b0bb).
⚠️ Report is 12 commits behind head on trunk.

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           
Flag Coverage Δ
multisite 70.38% <ø> (ø)
single 35.59% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions

github-actions Bot commented Jul 1, 2026

Copy link
Copy Markdown

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 props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: westonruter <westonruter@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@westonruter westonruter added the no milestone PRs that do not have a defined milestone for release label Jul 2, 2026
@westonruter westonruter requested a review from b1ink0 July 3, 2026 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no milestone PRs that do not have a defined milestone for release skip changelog PRs that should not be mentioned in changelogs [Type] Enhancement A suggestion for improvement of an existing feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant