Rework release workflow - #350
Merged
Merged
Conversation
GitHub does not fire release events for draft releases, so the release-prepare workflow could never trigger. Replace it with an interactive local script (bin/prepare-release.sh) that bumps versions, generates a changelog from merged PRs, and creates a release branch. Rework release-publish to build the plugin zip and create a GitHub release when the release PR is merged to trunk.
Versions with a hyphen (e.g., 2.3.0-beta.1) are marked as prerelease on the GitHub release. The WordPress.org deploy workflow skips these.
Member
Author
|
All green. I will test this one on trunk. |
JanJakes
added a commit
that referenced
this pull request
Apr 2, 2026
## Release `2.2.21` Version bump and changelog update for release `2.2.21`. **Changelog draft:** * Rework release workflow ([#350](#350)) * Monorepo setup + release automation ([#334](#334)) * Fix incorrect PHP polyfill implementations ([#338](#338)) **Full changelog:** v2.2.20...release/v2.2.21 ## Next steps 1. **Review** the changes in this pull request. 2. **Push** any additional edits to this branch (`release/v2.2.21`). 3. **Merge** this pull request to complete the release. Merging will automatically build the plugin ZIP, create a [GitHub release](https://github.com/WordPress/sqlite-database-integration/releases), and deploy to [WordPress.org](https://wordpress.org/plugins/sqlite-database-integration/).
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.
Summary
Replace the draft-release-triggered CI workflow with a local
prepare-release.shscript and a simplified publish workflow.GitHub does not fire
releaseevents for draft releases, so therelease-prepareworkflow could never trigger. The new approach uses a non-interactive script (bin/prepare-release.sh <version>) that bumps versions, generates a changelog from merged PRs, creates a release branch, and opens a PR. Merging the PR triggers the build and GitHub release automatically.Also adds pre-release support: versions with a hyphen (e.g.,
2.3.0-beta.1) are marked as pre-release and skip WordPress.org deployment.