feat(container): update docker.io/mariadb ( 11.4.8 → v11.8.5 ) #612
Conversation
homebot-0
bot
added
renovate
WalkthroughUpgrades MariaDB container image tag from 11.4.8 to 11.8.5 in the BookStack helm release. No configuration, logic, or behavioral changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
ℹ️ SOPS Encryption CheckNo SOPS files detected in this pull request.
No encryption validation required for this PR. |
✅ Gitleaks Secret Scan PassedNo secrets detected in this pull request.
|
--- kubernetes/apps/media/bookstack/app Kustomization: media/bookstack HelmRelease: media/bookstack-mariadb-standalone
+++ kubernetes/apps/media/bookstack/app Kustomization: media/bookstack HelmRelease: media/bookstack-mariadb-standalone
@@ -45,13 +45,13 @@
TZ: America/New_York
envFrom:
- secretRef:
name: bookstack-mariadb-standalone
image:
repository: docker.io/mariadb
- tag: 11.4.8
+ tag: 11.8.5
probes:
liveness:
custom: true
enabled: true
spec:
exec: |
--- HelmRelease: media/bookstack-mariadb-standalone Deployment: media/bookstack-mariadb-standalone
+++ HelmRelease: media/bookstack-mariadb-standalone Deployment: media/bookstack-mariadb-standalone
@@ -52,13 +52,13 @@
value: bookstack
- name: TZ
value: America/New_York
envFrom:
- secretRef:
name: bookstack-mariadb-standalone
- image: docker.io/mariadb:11.4.8
+ image: docker.io/mariadb:11.8.5
livenessProbe:
exec:
command:
- healthcheck.sh
- --connect
- --innodb_initialized |
homebot-0
bot
force-pushed
the
renovate/docker.io-mariadb-11.x
branch
from
5a1b506 to
67f3051
Compare
homebot-0
bot
changed the title
homebot-0
bot
force-pushed
the
renovate/docker.io-mariadb-11.x
branch
from
67f3051 to
b88b41e
Compare
homebot-0
bot
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
kubernetes/apps/media/bookstack/app/mariadb-helmrelease.yaml (1)
2-4: Stale version references in comments.Comments still reference
11.4.8but the image tag is now11.8.5. Update these to prevent documentation drift.📝 Proposed fix
--- -# Standalone MariaDB 11.4.8 for BookStack +# Standalone MariaDB 11.8.5 for BookStack # Uses official MariaDB image for exact version match with source data -# Source DB: MariaDB 11.4.8 (from VM 101 docker-sandbox2) +# Source DB: MariaDB 11.8.5
🤖 Fix all issues with AI agents
In `@kubernetes/apps/media/bookstack/app/mariadb-helmrelease.yaml`:
- Around line 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.
| repository: docker.io/mariadb | ||
| # renovate: datasource=docker depName=docker.io/mariadb versioning=semver | ||
| tag: 11.4.8 | ||
| tag: 11.8.5 |
There was a problem hiding this comment.
🧩 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:
- Test upgrade in staging with current BookStack version
- Backup/snapshot PVC before production deploy
- Run
ANALYZE TABLEon all tables post-upgrade to rebuild optimizer statistics - Review MariaDB 11.8 release notes and my.cnf for removed variables/plugins
- 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.
This PR contains the following updates:
11.4.8→11.8.5Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
🐘 MariaDB: Major versions may have breaking SQL syntax or config changes. Review release notes carefully before merging.
🐄 Talos CATTLE: Major/minor version requires manual approval. Full VM rebuild via Terraform.
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.