chore(deps): update docker.io/library/mariadb docker tag to v12

[renovate-bot-cbcoutinho]

This PR contains the following updates:

Package	Update	Change
docker.io/library/mariadb (source)	major	11.8.6-noble → 12.3.2-noble

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[claude]

Claude finished @renovate-bot-cbcoutinho[bot]'s task in 47s —— View job

---

PR Review: MariaDB 11 → 12 Major Version Bump

• Gather context and analyze PR
• Review docker-compose.yml change
• Check Nextcloud version in use
• Assess MariaDB 12 compatibility concerns
• Post final review

---

Change: docker-compose.yml line 6 — mariadb:11.8.6-noble → mariadb:12.3.2-noble with updated SHA256 digest.

What's Good

• SHA256 digest is correctly pinned and updated alongside the tag — proper security hygiene that prevents tag/digest mismatch.
• --transaction-isolation=READ-COMMITTED flag is preserved — this is required by Nextcloud and unchanged.
• Scope is limited to docker-compose.yml (dev/test environment only), so blast radius is low.
• SonarQube quality gate passes (no new issues).

Critical: Nextcloud Compatibility Check Required

The compose file itself flags this concern in the comment on line 5:

# Note: Check the recommend version here: https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html#server

The Nextcloud instance in use is 32.0.10 (docker-compose.yml:26). MariaDB 12.x is a brand-new major release series; as of this PR's creation, Nextcloud had historically certified against MariaDB 10.6, 10.11, and the 11.x LTS series. If Nextcloud 32.x has not added MariaDB 12.x to its compatibility matrix, this upgrade is premature even for a dev environment — issues could silently mask as CI failures without a clear root cause.

Recommendation

1. Verify Nextcloud 32.x system requirements list MariaDB 12.x as supported.
2. Confirm CI integration tests pass against this image — a green run covering the db container is a strong positive signal for practical compatibility.
3. If MariaDB 12 is not yet in the Nextcloud compatibility matrix, hold this PR and pin back to the latest stable 11.x LTS release until official support is confirmed.

Note: This PR has been open since late March 2026 (> 2 months). If CI has passed across multiple runs in that time, that provides reasonable confidence for a dev environment. However, the Nextcloud support page check is the definitive answer before merging to production-facing branches.

[claude]

PR Review: MariaDB 11 to 12 Major Version Bump

This Renovate PR updates MariaDB from 11.8.6-noble to 12.2.2-noble (a major version upgrade).

Key Concern: Nextcloud Compatibility

The docker-compose.yml already flags this with a comment pointing to the Nextcloud system requirements page. As of my knowledge cutoff, Nextcloud officially supported MariaDB 10.6, 10.11, and 11.4 (LTS). MariaDB 12 is a brand-new major release - verify Nextcloud supports it before merging, as major DB version bumps can break:

• SQL compatibility (syntax or behavior changes)
• Nextcloud DB schema checks (occ maintenance:repair)
• InnoDB/query planner behavior that silently affects correctness or performance

What to Check Before Merging:

1. Confirm Nextcloud supports MariaDB 12 via the system requirements link in docker-compose.yml. If not listed, this upgrade is premature.
2. Run CI/integration tests against MariaDB 12 - a green run is a strong positive signal.
3. Review MariaDB 12 release notes for breaking changes affecting READ-COMMITTED isolation or InnoDB behavior.

Minor Notes:

• SHA digest is correctly updated alongside the tag - good Renovate behavior.
• This may be fine for a dev/test environment if CI passes, but caution is warranted until Nextcloud explicitly lists MariaDB 12 support.

Recommendation: Verify Nextcloud officially supports MariaDB 12 (or confirm CI is green), then merge. If MariaDB 12 is not yet in the compatibility matrix, consider pinning back to the latest MariaDB 11 LTS.

[claude]

PR Review: MariaDB 11 → 12 Major Version Upgrade

This is a major version bump (11.8.6 → 12.2.2), which warrants closer scrutiny than a typical patch/minor update.

Compatibility Check Needed

The comment in docker-compose.yml itself flags this:

# Note: Check the recommend version here: https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html#server

The compose file uses Nextcloud 32.0.8. Before merging, it's worth verifying that Nextcloud 32.x officially lists MariaDB 12.x as a supported database version. MariaDB 12 is very new, and Nextcloud's compatibility matrix may not include it yet — if Nextcloud hasn't tested against MariaDB 12, this could introduce subtle data handling differences or compatibility issues in the dev/test environment.

What's Good

• SHA256 digest is properly pinned and updated — good security practice.
• Scope is limited to docker-compose.yml (dev/test environment only), so the blast radius is relatively low.

Recommendation

1. Check Nextcloud 32's system requirements to confirm MariaDB 12.x is listed as supported.
2. Confirm CI integration tests pass against this version (especially anything touching the db container directly).
3. If MariaDB 12 isn't yet listed as supported by Nextcloud, consider holding this update until it is — or pinning back to the latest stable 11.x release.

Otherwise the change itself is minimal and the approach is sound.

[claude]

PR Review: MariaDB 11 → 12 Major Version Bump

This is a Renovate Bot PR upgrading MariaDB from 11.8.6-noble to 12.2.2-noble. A few things worth considering before merging:

Nextcloud Compatibility (Critical)

The docker-compose.yml already includes a self-reminder:

# Note: Check the recommend version here: https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html#server

MariaDB 12 is a very new major release. As of April 2026, it's worth verifying that Nextcloud officially certifies against MariaDB 12.x before merging. Nextcloud's system requirements page has historically listed specific supported MariaDB versions (e.g. 10.6, 10.11, 11.4 LTS series). If MariaDB 12 isn't yet on that list, running it in the dev/test environment could mask incompatibilities that wouldn't be caught until production.

Major Version Upgrade Risks

A 11.x → 12.x jump can include:

• Changed SQL mode defaults
• Deprecated/removed functions or syntax
• Changed default character set or collation behavior
• New reserved keywords that could conflict with Nextcloud's schema

The --transaction-isolation=READ-COMMITTED flag used in this compose file should remain valid, but worth confirming nothing in MariaDB 12 affects the transaction semantics Nextcloud depends on.

What's Good

• The SHA256 digest pin is correctly updated alongside the tag — this is good security hygiene and prevents tag mismatch issues.
• Single-line change, easy to review and revert if needed.

Recommendation

Before merging, I'd suggest:

1. Verifying the Nextcloud system requirements page lists MariaDB 12 as supported.
2. Running the full integration test suite (uv run pytest -m "integration and not oauth") against this upgraded image to catch any SQL compatibility issues.
3. Checking the MariaDB 12 release notes for any breaking changes relevant to Nextcloud's usage patterns.

If the CI pipeline runs integration tests against Docker Compose and they pass, that's a good signal — but the Nextcloud compatibility question is worth an explicit check given the comment already in the file.

---

Review generated by Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud