The main upgrade to louislam/uptime-kuma:2.4.0 and mariadb:12.3 was already merged upstream (commits 47f5a98 and 51d0284). This PR adds the missing MARIADB_AUTO_UPGRADE=1 env var to compose.mariadb.yml, which ensures safe in-place upgrades for operators moving from MariaDB 11.x → 12.x.
Note: cc-ci tests use the SQLite path (compose.yml only), so this overlay change passes CI via the existing test suite.
The main upgrade to louislam/uptime-kuma:2.4.0 and mariadb:12.3 was already merged upstream (commits 47f5a98 and 51d0284). This PR adds the missing `MARIADB_AUTO_UPGRADE=1` env var to `compose.mariadb.yml`, which ensures safe in-place upgrades for operators moving from MariaDB 11.x → 12.x.
Note: cc-ci tests use the SQLite path (compose.yml only), so this overlay change passes CI via the existing test suite.
cc @trav @notplants
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The main upgrade to louislam/uptime-kuma:2.4.0 and mariadb:12.3 was already merged upstream (commits
47f5a98and51d0284). This PR adds the missingMARIADB_AUTO_UPGRADE=1env var tocompose.mariadb.yml, which ensures safe in-place upgrades for operators moving from MariaDB 11.x → 12.x.Note: cc-ci tests use the SQLite path (compose.yml only), so this overlay change passes CI via the existing test suite.
cc @trav @notplants
!testme
🌻 cc-ci —
uptime-kuma@eb4521cc✅ passedfull logs · dashboard
!testme
🌻 cc-ci —
uptime-kuma@eb4521cc✅ passedfull logs · dashboard
eb4521cc5dtob0ce7942c7chore: upgrade to 3.1.0+2.4.0to chore: add MARIADB_AUTO_UPGRADE=1 to mariadb overlay!testme
🌻 cc-ci —
uptime-kuma@b0ce7942✅ passedfull logs · dashboard
Pull request closed