chore: upgrade to 4.0.0+2.4.0 #1
Reference in New Issue
Block a user
No description provided.
Delete Branch "upgrade-4.0.0+2.4.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
uptime-kuma: 2.2.1 → 2.4.0 + mariadb 11.8 → 12.2
Image tag table
Recipe version bump
3.0.0+2.2.1 → 4.0.0+2.4.0 (major bump: mariadb 11→12 is a major dependency version change)
Changes 2.2.1 → 2.4.0 (uptime-kuma)
No breaking changes for standard Docker deployments.
Operator Action Required — mariadb 11.8 → 12.2
This is a MAJOR version upgrade. MariaDB 12.x removes legacy features not used by this recipe (query cache, big_tables var, slave_parallel_mode, legacy auth plugins). No compose changes needed.
In-place upgrade: ensure mariadb-upgrade runs on first container start (handled automatically by the official Docker image).
Risks
Tested on the cc-ci recipe CI server. NOT merged — for operator review.
cc @trav @notplants
!testme
!testme
🌻 cc-ci —
uptime-kuma@72861889✅ passedfull logs · dashboard
Pull request closed