Skip to content

feat(container)!: Update docker.io/mariadb ( 11.4.8 → v12 ) #626

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 → v12 ) #626

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: 12.1.2
env:
Comment on lines 27 to 31
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

🏁 Script executed:

cat -n kubernetes/apps/media/bookstack/app/mariadb-helmrelease.yaml

Repository: jlengelbrecht/prox-ops

Length of output: 3930

🌐 Web query:

MariaDB 12.1.2 release notes breaking changes from 11.4 upgrade

💡 Result:

Short answer: MariaDB 12.1.2’s release notes do not list a dedicated “breaking changes when upgrading from 11.4” section — the 12.1.2 notes focus on new features, bugfixes and individual changelog items (see release notes and changelog). You must therefore treat the upgrade as a major-version upgrade and follow the usual incompatible-change checks (remove/rename deprecated config options, run mariadb-upgrade, and verify mysql system tables and any table-format changes). Key references:

  • MariaDB 12.1.2 release notes / changelog (no single “upgrade-from-11.4 breaking changes” list; lists individual changes such as removal of @@new_mode=FIX_INDEX_STATS_FOR_ALL_NULLS and other MDEV items). [1][2]
  • MariaDB upgrade documentation and “Incompatible Changes” for major upgrades (examples of removed options that must be removed from my.cnf when upgrading to 11.4 — same principle applies when moving between major releases; run mariadb-upgrade and review incompatible-options). [3][4]
  • Downgrade is not supported between major versions; verify mysql schema and on-disk format changes before upgrade. [5]

Recommended action before upgrading 11.4 → 12.1.2:

  1. Read the 12.1.2 release notes + changelog for any MDEV items that affect features you use (search the changelog for relevant MDEV IDs). [1][2]
  2. Review the “Incompatible Changes”/upgrade docs and remove deprecated/removed options from your config (example list shown in 11.4 docs). [3]
  3. Backup data, run mariadb-upgrade after starting the new server, and test on staging (downgrade between majors is unsupported). [4][5]

Sources:
[1] MariaDB 12.1.2 Release Notes.
[2] MariaDB 12.1.2 Changelog.
[3] Upgrade / Incompatible changes (example: Upgrade to 11.4 — removed/renamed options).
[4] mariadb-upgrade documentation.
[5] Downgrading between major versions (not supported).

Major MariaDB bump (11.4.8 → 12.1.2): verify incompatible changes and plan pre-deployment testing.

MariaDB 12.1.2 has no single "breaking changes" guide; you must review the 12.1.2 changelog for MDEV items affecting BookStack's queries and audit my.cnf for removed/renamed options in the Incompatible Changes documentation. Run mariadb-upgrade after upgrading and test backup/restore on staging—downgrade between major versions is unsupported.

Additionally, lines 2-4 still reference MariaDB 11.4.8 in the header comments; update them to reflect 12.1.2.

🤖 Prompt for AI Agents 
In `@kubernetes/apps/media/bookstack/app/mariadb-helmrelease.yaml` around lines 27
- 31, The HelmRelease bumps MariaDB to tag "12.1.2" but you must verify
incompatible changes: review MariaDB 12.1.2 changelog for MDEV items affecting
BookStack queries, audit my.cnf for removed/renamed options per the
"Incompatible Changes" docs, and plan to run mariadb-upgrade and full
backup/restore tests on staging before promoting (address any SQL or config
incompatibilities found). Also update the header comments that still reference
"11.4.8" to "12.1.2" so the file header matches the image tag, and document the
pre-deploy test plan/results in the PR notes.

TZ: America/New_York
MARIADB_DATABASE: bookstackapp
Expand Down