ci(wordpress): publish to WordPress.org on merge, then GitHub release and Discord - #57
Merged
Merged
Conversation
…lease on GitHub and announce on Discord
bendersej
added a commit
that referenced
this pull request
Sep 29, 2026
## Background The Embed and React workflows watched all of `scripts/`, so a change to the WordPress release scripts (#57) built and tested both SDKs for nothing. ## Changes - Embed and React run for `scripts/check-api.mjs` and `scripts/check-exports.mjs` only, the two shared scripts their packages call (`check:api`, `check:exports`); their own folders and the root package files still trigger them as before
bendersej
added a commit
that referenced
this pull request
Sep 29, 2026
## Background Releasing the plugin is now merge-only (#57), except one manual step: committing `wordpress/svn/tags/<version>/` to git after each release, as a copy of WordPress.org. Every release is already recorded as a `wordpress@<version>` GitHub release on the commit it was published from, so the copy duplicates that history. ## Changes - `wordpress/svn/tags/` leaves git and is ignored (the manual SVN fallback still creates it locally) - The release steps in `wordpress/README.md` end at "Merge", and say where published versions are recorded ## Notes - Merging touches `wordpress/svn/`, so the WordPress release workflow runs: 1.2.1 is already published and the readme and assets match, so it publishes and announces nothing (the publish preview on this PR shows the same)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
Releasing the WordPress plugin meant a manual SVN commit with the operator's credentials, then running the release workflow by hand once WordPress.org caught up.
Changes
mainpublishes:scripts/publish-wordpress-svn.shchecks the three version strings agree, then publishes a new Stable tag (trunk, assets,tags/<version>) or, for a version already out, syncs only the readme and the listing assetswordpress@<version>GitHub release and posts the changelog to Discord; re-runs publish and announce nothing twicewordpress-orgenvironment deployable frommainwordpress/README.mddescribes the automatic flow, with the manual SVN steps as a fallbackNotes
main(1.2.0, already published) reports nothing to publish; the 1.2.1 branch lists exactly the 1.2.1 release; a mismatched version fails before touching SVNwordpress-orgenvironment withSVN_USERNAMEandSVN_PASSWORDbefore the first merge that changeswordpress/svn/