Skip to content

feat(container): update docker.io/mariadb ( 11.4.8 → v11.8.5 ) #612

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
homebot-0 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(container): update docker.io/mariadb ( 11.4.8 → v11.8.5 ) #612

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion kubernetes/apps/media/bookstack/app/mariadb-helmrelease.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ spec:
image:
repository: docker.io/mariadb
# renovate: datasource=docker depName=docker.io/mariadb versioning=semver
tag: 11.4.8
tag: 11.8.5
Comment on lines 28 to +30
Copy link

@coderabbitai coderabbitai bot Jan 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

MariaDB 11.8 breaking changes from 11.4 compatibility

💡 Result:

Short summary of notable breaking / compatibility-impacting changes when moving from MariaDB 11.4 -> 11.8

  • System-versioned (temporal) tables: row/index timestamp range is extended (to ~2106); upgrading requires rewriting those rows/indexes and can take a long time for large tables — downgrading is non‑trivial if you upgrade system‑versioned tables. [1][2]

  • New/changed data types and indexes: native VECTOR(N) datatype and VECTOR INDEX (vector functions and distance functions). New types/indexes can affect storage/backup/replication compatibility with older servers. [1][3]

  • Optimizer/plan changes and statistics: optimizer rewrites in the 11.x line continue to change execution plans; you should ANALYZE TABLE after upgrade and validate critical queries. [1]

  • Binary/tool name and client changes: client binary names (mariadb / mariadb-dump / mariadb-admin) and related behavior continue to be preferred over the historical mysql/mysqldump names — automation/scripts may need updating. [1]

  • Replication/GTID and binary-log behavior: stricter GTID/replication behaviors and some event ordering/logging changes; verify replication topology compatibility before upgrading. [1][2]

  • Removed/changed variables and plugins: certain legacy variables/functions/plugins removed or changed between 11.4 and 11.8 (review your my.cnf and installed plugins; remove deprecated configs before starting). [1]

  • InnoDB / storage-format changes: internal InnoDB metadata/redo-log and other InnoDB behaviour continued to evolve in 11.x — ensure backups and mariabackup compatibility; check for case-sensitivity fixes on Windows data dictionary. [2][1]

  • Temporary files/tables limits and other server defaults: new options and changed defaults (e.g., limits for temp files/tables) that may affect resource usage and require tuning. [3][1]

Recommended actions

  • Read the full 11.8 release notes and “Changes & Improvements in MariaDB 11.8”. Test upgrade in staging, run mariadb-upgrade/mariadb-upgrade utility, BACKUP (logical backup recommended for safety), ANALYZE TABLE, and validate replication and critical queries. [1][2]

Sources

  • Changes & Improvements in MariaDB 11.8 (release notes / upgrade notes). [1]
  • MariaDB 11.8 release notes / changelog (11.8.x). [2]
  • What's New in MariaDB Enterprise Server 11.8 (vector, limits, enterprise-specific notes). [3]

If you want, I can produce a concise checklist tailored to your environment (system‑versioned tables, replication, mariabackup usage, OS) — tell me which features you use.

🌐 Web query:

BookStack MariaDB 11.8 version compatibility requirements

💡 Result:

Short answer: BookStack's documented minimum MariaDB requirement is MariaDB >= 10.6; MariaDB 11.8 is a newer MariaDB release and will generally be compatible, but because MariaDB 11 introduces some incompatibilities vs MySQL 8.0 you should test upgrades and take backups first.

Sources:

  • BookStack installation / requirements (MariaDB >= 10.6). [1]
  • BookStack update notes (minimum DB version changed to MariaDB 10.6). [2]
  • MariaDB release/compatibility notes (differences between MariaDB 11.x and MySQL 8.0 / 11.8 release). [3][4]

If you want, I can check your specific BookStack version and list any known incompatibilities or migration steps.

Verify MariaDB 11.4 → 11.8.5 upgrade path for BookStack compatibility.

This is a significant jump with real breaking changes: system-versioned (temporal) tables require in-place index/row rewriting (potentially slow on large tables), new VECTOR datatype/INDEX, optimizer plan shifts, stricter replication/GTID semantics, InnoDB metadata evolution, and removed/changed variables. BookStack nominally supports MariaDB ≥10.6, but MariaDB 11.x introduces incompatibilities vs MySQL 8.0. Existing PVC data will be upgraded on pod restart; mariadb-upgrade must run successfully.

Pre-merge validation:

  1. Test upgrade in staging with current BookStack version
  2. Backup/snapshot PVC before production deploy
  3. Run ANALYZE TABLE on all tables post-upgrade to rebuild optimizer statistics
  4. Review MariaDB 11.8 release notes and my.cnf for removed variables/plugins
  5. Validate replication topology if used
🤖 Prompt for AI Agents 
In `@kubernetes/apps/media/bookstack/app/mariadb-helmrelease.yaml` around lines 28
- 30, The HelmRelease currently pins the MariaDB image at "tag: 11.8.5"
(repository: docker.io/mariadb) which is a major upgrade from the supported
range for BookStack; before merging, test the upgrade path in staging using the
same BookStack release, snapshot the PVC, run mariadb-upgrade on the data volume
during a staged restart, then run ANALYZE TABLE on all tables, review MariaDB
11.8 release notes/my.cnf for removed variables/plugins and validate any
replication/GTID topology; only proceed to update the tag in
mariadb-helmrelease.yaml once these checks pass.

env:
TZ: America/New_York
MARIADB_DATABASE: bookstackapp
Expand Down