Open
Conversation
Member
JanJakes
added a commit
that referenced
this pull request
Mar 31, 2026
## Summary
This PR restructures the repository into a **monorepo** with separate
packages and adds **release automation**.
### Monorepo structure
```
packages/
├── mysql-on-sqlite/ # MySQL-on-SQLite driver
├── mysql-proxy/ # MySQL binary protocol proxy
└── plugin-sqlite-database-integration/ # WordPress plugin
```
The plugin package links to the driver through a `wp-includes/database`
symlink. The release build script (`composer run build`) resolves this
symlink into a real copy, producing a self-contained plugin zip.
WordPress setup for WP tests remains at the repository root for now. The
tests for the legacy driver remain there as well (to be deleted soon).
We eventually split it even further (`mysql-parser`, ...) and handle the
grammar tools, but that can be addressed separately.
### Automated release workflow
Release is automated with GitHub Actions. It requires only two manual
steps:
1. **Create a draft release with a new tag and changelog.**
The `release-prepare` workflow will automatically:
- Use the draft tag to bump versions in `version.php`, `load.php`, and
`readme.txt`.
- Add the draft release changelog entry to `readme.txt`.
- Build the plugin ZIP and attach it to the draft release.
- Create a PR (`release/<version>` → `trunk`) and link it in the draft
release body.
2. **Review and merge the PR.**
The `release-publish` workflow will automatically:
- Publish the draft release.
- Publish the release artifact to WordPress.org.
Closes
#83,
#200, and
#328.
Note that currently, the release workflow is aimed at releasing the
SQLite plugin, which goes hand-in-hand with the driver changes. If we
need to decouple the releases at some point (e.g., release a new driver
version, but not plugin, or release the plugin only), then we'll need to
address that.
### Testing
I will test and fine-tune the release workflow on `trunk` using a
temporary nonsense tag (`0.0.1-test1`, etc.). The WordPress.org part
requires SVN credentials, and I will test and fine-tune it with the next
plugin release.
### Next steps
- Update Playground plugin-refresh logic once this is merged.
- Update Studio to use the new release artifacts starting from the next
release.
- Further split the components (`mysql-parser`, ...).
- Improve the monorepo setup tooling (do we need anything like NX?).
- Set up Composer packages.
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
2 participants
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
Testing