From 7a7c30c1015ee3aae56b51da905328657a9a6e29 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20Jakes=CC=8C?= Date: Thu, 8 Oct 2026 16:09:21 +0200 Subject: [PATCH 1/2] Prepare release 3.1.0 --- packages/mysql-on-sqlite/src/version.php | 2 +- packages/plugin-sqlite-database-integration/load.php | 2 +- .../plugin-sqlite-database-integration/readme.txt | 11 ++++++++++- 3 files changed, 12 insertions(+), 3 deletions(-) diff --git a/packages/mysql-on-sqlite/src/version.php b/packages/mysql-on-sqlite/src/version.php index b547cdd80..7d08377f8 100644 --- a/packages/mysql-on-sqlite/src/version.php +++ b/packages/mysql-on-sqlite/src/version.php @@ -9,4 +9,4 @@ * * This constant needs to be updated on plugin release! */ -define( 'SQLITE_DRIVER_VERSION', '3.0.2' ); +define( 'SQLITE_DRIVER_VERSION', '3.1.0' ); diff --git a/packages/plugin-sqlite-database-integration/load.php b/packages/plugin-sqlite-database-integration/load.php index aa3d94b50..ad5d08bd8 100644 --- a/packages/plugin-sqlite-database-integration/load.php +++ b/packages/plugin-sqlite-database-integration/load.php @@ -3,7 +3,7 @@ * Plugin Name: SQLite Database Integration * Description: SQLite database driver drop-in. * Author: The WordPress Team - * Version: 3.0.2 + * Version: 3.1.0 * Requires PHP: 7.2 * Network: true * License: GPL-2.0-or-later diff --git a/packages/plugin-sqlite-database-integration/readme.txt b/packages/plugin-sqlite-database-integration/readme.txt index 8386aa744..b46950cdc 100644 --- a/packages/plugin-sqlite-database-integration/readme.txt +++ b/packages/plugin-sqlite-database-integration/readme.txt @@ -4,7 +4,7 @@ Contributors: wordpressdotorg, aristath, janjakes, zieladam, berislav.grgic Requires at least: 6.4 Tested up to: 7.1 Requires PHP: 7.2 -Stable tag: 3.0.2 +Stable tag: 3.1.0 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Tags: sqlite, database @@ -91,6 +91,15 @@ Yes. The plugin replaces the default MySQL-based database layer with an SQLite-b == Changelog == += 3.1.0 = + +* Document SQLite database storage and `DB_PATH` ([#520](https://github.com/WordPress/sqlite-database-integration/pull/520)) +* Fix `utf8mb4_0900_ai_ci` collation in tables created by WordPress ([#514](https://github.com/WordPress/sqlite-database-integration/pull/514)) +* Support composite `TRADITIONAL` SQL mode ([#509](https://github.com/WordPress/sqlite-database-integration/pull/509)) +* Fix `IF()` condition evaluation ([#518](https://github.com/WordPress/sqlite-database-integration/pull/518)) +* Support `DB_PATH` as the primary database path constant ([#512](https://github.com/WordPress/sqlite-database-integration/pull/512)) +* Add randomized SQLite database storage ([#502](https://github.com/WordPress/sqlite-database-integration/pull/502)) + = 3.0.2 = * Fix schema reconstruction with native numeric results ([#506](https://github.com/WordPress/sqlite-database-integration/pull/506)) From fe9657009601f575c31b0b4a2fe22bb1891a0344 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20Jakes=CC=8C?= Date: Thu, 8 Oct 2026 16:40:29 +0200 Subject: [PATCH 2/2] Expand the 3.1.0 changelog Mirror the approved release notes using the readme.txt formatting from 3.0.0. https://github.com/WordPress/sqlite-database-integration/pull/521 --- .../readme.txt | 46 ++++++++++++++++--- 1 file changed, 40 insertions(+), 6 deletions(-) diff --git a/packages/plugin-sqlite-database-integration/readme.txt b/packages/plugin-sqlite-database-integration/readme.txt index b46950cdc..bd71661a2 100644 --- a/packages/plugin-sqlite-database-integration/readme.txt +++ b/packages/plugin-sqlite-database-integration/readme.txt @@ -93,12 +93,46 @@ Yes. The plugin replaces the default MySQL-based database layer with an SQLite-b = 3.1.0 = -* Document SQLite database storage and `DB_PATH` ([#520](https://github.com/WordPress/sqlite-database-integration/pull/520)) -* Fix `utf8mb4_0900_ai_ci` collation in tables created by WordPress ([#514](https://github.com/WordPress/sqlite-database-integration/pull/514)) -* Support composite `TRADITIONAL` SQL mode ([#509](https://github.com/WordPress/sqlite-database-integration/pull/509)) -* Fix `IF()` condition evaluation ([#518](https://github.com/WordPress/sqlite-database-integration/pull/518)) -* Support `DB_PATH` as the primary database path constant ([#512](https://github.com/WordPress/sqlite-database-integration/pull/512)) -* Add randomized SQLite database storage ([#502](https://github.com/WordPress/sqlite-database-integration/pull/502)) +**SQLite Database Integration 3.1 is here! 🎉** + +This release improves **database storage and configuration** and fixes several MySQL compatibility issues. + +**What's new** + +Version 3.1 improves how WordPress sites store, locate, and protect their SQLite databases. It also fixes SQL behavior and export compatibility: + +* **Randomized database paths:** The default database location is now a randomized directory under `wp-content/database/`, recorded in `wp-content/database/db-path.php`. ([#502](https://github.com/WordPress/sqlite-database-integration/pull/502)) +* **`DB_PATH`:** Configure the database with one full-path constant, also available at runtime for integrations. ([#512](https://github.com/WordPress/sqlite-database-integration/pull/512)) +* **SQL compatibility:** Fix `IF()` condition evaluation and make `TRADITIONAL` enable its component SQL modes. ([#518](https://github.com/WordPress/sqlite-database-integration/pull/518), [#509](https://github.com/WordPress/sqlite-database-integration/pull/509)) +* **WordPress table collations:** Default to `utf8mb4_unicode_520_ci` for new tables created with WordPress's charset settings, improving exports to MariaDB. Existing tables keep their recorded collation. ([#514](https://github.com/WordPress/sqlite-database-integration/pull/514)) +* **Documentation:** A new plugin README and expanded FAQ explain database storage and secure configuration. ([#520](https://github.com/WordPress/sqlite-database-integration/pull/520)) + +For more information about database paths and secure configuration, read the [database storage guide](https://github.com/WordPress/sqlite-database-integration/blob/trunk/packages/plugin-sqlite-database-integration/README.md#database-storage). + +**Upgrading to 3.1** + +Upgrading an existing SQLite site is straightforward: + +1. **Back up** your SQLite database. +2. **Update the plugin** to version 3.1. + +Existing `.ht.sqlite` and `.ht.sqlite.php` databases move to the randomized layout automatically unless a database file path is explicitly configured. + +To properly **secure the database**, set `DB_PATH` in `wp-config.php` to an absolute file path outside the web root that your web server does not expose. Its directory must be writable by PHP. Changing `DB_PATH` does not move an existing database. + +**Breaking changes** + +Review these changes if you use custom database settings or integrations: + +* **Database paths:** Default database files now move to randomized paths under `wp-content/database/`. Explicitly configured file paths stay unchanged. Integrations, including backup and migration tools, must read `DB_PATH` after WordPress loads instead of assuming a fixed filename. +* **Legacy constants:** `DB_DIR` and `DB_FILE` are now deprecated. They and the previously deprecated `FQDB` and `FQDBDIR` remain supported, but `DB_PATH` takes precedence. Conflicting values trigger warnings. +* **Absolute paths:** Relative database file and directory paths are now rejected. `:memory:` remains available for in-memory databases. + +**Thank you** + +Thank you to everyone who contributed, tested, and helped update integrations. + +**Changes since 3.0.2:** [`v3.0.2...v3.1.0`](https://github.com/WordPress/sqlite-database-integration/compare/v3.0.2...v3.1.0) = 3.0.2 =