fix(ci): sync info.json changelog from readme.txt on release#2459
Conversation
The release manifest generator patched version and compatibility fields but never rewrote sections.changelog, so the changelog was inherited unchanged from the previously published manifest and went stale. Extract the Changelog section from readme.txt (the source of truth, already trimmed with a View the full changelog link) and write it into the manifest.
|
📦 Next.js Bundle Analysis for @faustwp/getting-started-exampleThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
There was a problem hiding this comment.
Pull request overview
Updates the plugin release manifest generation so info.json reflects the current release notes by syncing the changelog from plugins/faustwp/readme.txt during release-time processing (addresses the “info.json changelog goes stale” portion of #2458).
Changes:
- Extract the
== Changelog ==section body fromreadme.txtduring the release workflow script. - Populate
info.json’s.sections.changelogviajqwhen a non-empty changelog is found.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| changelog=$(awk ' | ||
| /^== Changelog ==/ { capture = 1; next } | ||
| capture && /^== / { capture = 0 } | ||
| capture { body = body $0 "\n" } |
Regenerate the release manifest's changelog from readme.txt during the release so info.json reflects the current release notes instead of a stale inherited value (part of #2458).