ci: replace changesets with release-please - #2566
josephfusco wants to merge 1 commit into
Conversation
Version and publish all four npm packages and the FaustWP plugin with release-please. The release workflow now calls the wordpress.org deploy directly, since tags created with GITHUB_TOKEN don't trigger other workflows. Drops the nightly canary publish, which has failed on every run since changeset stopped resolving on PATH.
|
📦 Next.js Bundle Analysis for @faustwp/getting-started-exampleThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
247.07 KB (🟡 +12 B) |
Details
The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
This branch has not been deployed
1 participant
Related: #2458
Merge #2530 first (this deletes its two pending changesets), then rebase and set
bootstrap-shaand the manifest to the post-#2530 commit and versions. npm trusted publishing should keep working becausenpm-publish.ymlis still called fromrelease-packages.yml, but the first real release is the only true test of that. The plugin sync commit is pushed withGITHUB_TOKEN, so CI won't re-run on the release PR after it lands.Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Assisting with the release-please config and workflows, adapting the plugin readme sync script, and updating the release docs.