NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist · #2468 most downloaded on Packagist
WorDBless allows you to use WordPress core functions in your PHPUnit tests without having to set up a database and the whole WordPress environment
Last release 1 months ago
18 Aug 2026
Release timing varies
gaps range from 3 weeks to 1.9 years
Most releases are documented
notes for 10 of 13 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
13 releases · first in 2020
Bump phpunit/phpunit from 9.6.22 to 9.6.33 by @dependabot [bot] in #82
The roots/wordpress constraint is now ^6.6 || ^7.0, so projects using WorDBless can run their tests against WordPress 7.0. This is the headline change: 0.6.0 capped you at WordPress 6.x, and the widened constraint has been sitting on trunk untagged since February.
CI now runs all three test suites against pinned WordPress 6.6 and 7.0 legs in addition to the lowest/locked/highest matrix, so neither major loses coverage when the next one ships.
Metadata for users is now cleared between tests, matching what already happened for options, posts, post meta, and users. If a test relied on user meta surviving from one test method to the next, it will need to set that meta up explicitly.
WorDBless\Composer\InstallDropin::copy() now takes the Composer Event object and reads extra.wordpress-install-dir from the root package, so a custom WordPress install directory gets the db.php drop-in in the right place. Used as documented, as a post-install-cmd and post-update-cmd script handler, this needs no change on your side. Any code calling InstallDropin::copy() directly will need to pass the event.
The SQLite cleanup in Load::load() only runs for the sqlite engine now, and ABSPATH is defined before it runs.
Full Changelog: 0.6.0...0.6.1
One column per quarter.
Experimental: Add support for SQLite by @kraftbj in #74
This allows WorDBless to work in two modes -- no database (default) or with SQLite by passing an argument to the Load::init() function. This uses the SQLite implementation plugin being developed for potential Core inclusion. A known issue is that the SQLite plugin does not expect to be used for new installs without an existing MySQL database, so the first run of using SQLite will emit some noise about the DB not being found until it switches over to attempting SQLite.
Full Changelog: 0.5.3...0.6.0
Fix get_metadata( $single = true ) when the default is an array by @anomiex in #79
Full Changelog: 0.5.2...0.5.3
Metadata: Fix return value for Metadata::get when $single is true by @manzoorwanijk in #77
$single is true by @manzoorwanijk in #77Full Changelog: 0.5.1...0.5.2
BaseTestCase: Add attributes for PHPUnit 11+ by @anomiex in #75
Full Changelog: 0.5.0...0.5.1
Move phpunit-polyfills to dev-requirements by @heiglandreas in #66
Full Changelog: 0.4.2...0.5.0
Use Yoast PHPUnit Polyfill by @kraftbj in #61
Full Changelog: 0.4.1...0.4.2
Use TAB characters in README by @szepeviktor in #57
Full Changelog: 0.4.0...0.4.1
The package that WorDBless pulls WordPress updated their process to no longer ship the wp-content directory, which means no longer will all the defaul
The package that WorDBless pulls WordPress updated their process to no longer ship the wp-content directory, which means no longer will all the default themes from Twenty Ten onward will be downloaded!
The downside is this breaks the historical way WorDBless is installed.
When updating to 0.4.0, you will need to update your package's composer.json to use the new command:
"scripts": {
"post-install-cmd": "WorDBless\\Composer\\InstallDropin::copy",
"post-update-cmd": "WorDBless\\Composer\\InstallDropin::copy"
},
Thanks to @oskosk, @lhkowalski, and @dkmyta for the original report.
Full Changelog: 0.3.1...0.4.0
Fixes update_option for default options and fix wp_untrash_post tests for WordPress 5.6
Fixes update_option for default options and fix wp_untrash_post tests for WordPress 5.6
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →