2026.10.12-r1 — SQLite Database Integration 3.1.0

Changed

• Upgraded SQLite Database Integration from 3.0.2 to 3.1.0, pinned to
  upstream commit 6546e4538b708a1d8a565a1d31688bd63b610fa3.
• Refreshed the pinned WordPress 7.1.0/PHP 8.5 Apache base manifest digest
  to match the current official image required by the upstream release gate.
• Included randomized default database storage, the DB_PATH configuration
  constant, SQL IF() and TRADITIONAL mode fixes, and improved table
  collation defaults for MariaDB exports.
• Updated SQLite Diagnostics to prefer the runtime DB_PATH while retaining
  compatibility with the legacy FQDB constant.

Upgrade notes

• Back up the entire wp-content/database/ directory before upgrading.
  Default legacy databases migrate automatically to a randomized directory;
  preserve db-path.php and the database's WAL/SHM sidecars on the same volume.
• Read DB_PATH after WordPress loads for backup and migration integrations.
  Explicit paths remain unchanged. Configure an absolute persistent path
  outside the web root; changing DB_PATH does not move existing data.
• DB_DIR and DB_FILE are deprecated, conflicting legacy constants warn,
  and relative database paths are rejected.

Images: soulteary/sqlite-wordpress:2026.10.12-r1 and ghcr.io/soulteary/sqlite-wordpress:2026.10.12-r1. Published successfully for amd64, arm64, arm/v7, arm/v6, and arm/v5. Both registries share manifest digest sha256:e060cc1abb7940bb2e50c4e54ded85b6dbd7fd66d7361f249180d36125e9e373. Per-platform SBOM/provenance and both registry signatures passed verification. The 2026.10.12 and latest aliases were promoted successfully.

Full changelog: 2026.09.10-r1...2026.10.12-r1