Skip to content

fix(release): require WordPress changelog entries - #51

Merged
DavidBabinec merged 4 commits into
mainfrom
fix/wp-release-changelog
Oct 27, 2026
Merged

DavidBabinec merged 4 commits into
mainfrom
fix/wp-release-changelog

Conversation

@DavidBabinec

Copy link
Copy Markdown
Contributor

Fixes #29

The bug

WordPress's plugin readme stopped at 2.0.1 while the stable tag was 2.0.2. Linking to GitHub did not give users the update notes inside WordPress.

The fix

Restore the five 2.0.2 release notes, including the font re-save instruction. Reject packages with a missing or empty readme changelog entry for their version, and add this requirement to the release checklist.

Verification

The builder rejects the original readme and an empty version entry before building. The fixed readme is included unchanged in the ZIP.

Web tests: 206 passed; PHP: 48 tests, 116 assertions
WordPress release build and Docker E2E: passed
Missing-entry and empty-entry controls: rejected as expected
Changed-script Biome check: passed

Notes

WordPress.org receives these notes when the next release is published. No version bump or publication is included.

The shared import handler replaced local file data with a Google Fonts request before the custom-aware uploader could run. Preserve local data and report local upload failures with the right error.
The 2.0.2 readme omitted its release notes, leaving plugin details on 2.0.1. Restore those notes and reject future packages whose readme lacks a non-empty entry for the version being built.
@DavidBabinec
DavidBabinec marked this pull request as ready for review October 27, 2026 10:16
@DavidBabinec
DavidBabinec merged commit 0d3627e into main Oct 27, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Update your change log with each release

1 participant