chore(uptime-kuma): bump image to :2

The :1 image runs Node 18 (EOL), which gets no fix for the October 2026
Node.js security release. :2 migrates kuma.db in place on first start;
back up kuma_data per host before pulling (see plan/10-uptime-kuma.md).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docker-compose.yml

@@ -376,7 +376,7 @@ services:
   # Status monitoring + public status page. caddy proxies status. -> :3001.
   # Joins mcnet so monitors probe the stack by internal service name.
   uptime-kuma:
-    image: louislam/uptime-kuma:1
+    image: louislam/uptime-kuma:2
     container_name: uptime-kuma
     restart: unless-stopped
     volumes:

mods-sides.json

@@ -74,6 +74,7 @@
   "coroutil-neoforge-1.21.0-1.3.9.jar": "both",
   "corpse-neoforge-1.21.1-1.1.13.jar": "both",
   "corpsecurioscompat-1.21.1-NeoForge-4.0.1.jar": "both",
+  "craftabletotemofundying-1.21.1-0.1.jar": "both",
   "create-1.21.1-6.0.10.jar": "both",
   "create-central-kitchen-2.5.0.jar": "both",
   "create-enchantment-industry-2.4.1.jar": "both",
@@ -112,6 +113,7 @@
   "ferritecore-7.0.3-neoforge.jar": "both",
   "fishingoverhaul-1.21.1-1.2.1.jar": "both",
   "flightapi-neoforge-1.1.1.jar": "both",
+  "friendsforlife-1.2.1.jar": "both",
   "ftb-chunks-neoforge-2101.1.17.jar": "both",
   "ftb-essentials-neoforge-2101.1.9.jar": "both",
   "ftb-library-neoforge-2101.1.33.jar": "both",
@@ -149,6 +151,7 @@
   "moonlight-neoforge-1.21.1-3.0.22.jar": "both",
   "morefunctionalstorage-1.2.3.jar": "both",
   "moreoverlays-1.24.2-mc1.21.1-neoforge.jar": "client",
+  "owo-lib-neoforge-0.12.15.5-beta.1+1.21.jar": "both",
   "polymorph-neoforge-1.1.0+1.21.1.jar": "both",
   "ponderjs-neoforge-1.21.1-2.4.0.jar": "client",
   "rechiseled-1.2.5-neoforge-mc1.21.jar": "both",
@@ -162,7 +165,7 @@
   "sliceanddice-forge-4.2.4.jar": "both",
   "smartfeedingtroughs-neoforge-1.21.1-1.2.0.jar": "both",
   "sodium-extra-neoforge-0.8.7+mc1.21.1.jar": "client",
-  "sodium-neoforge-0.8.12-alpha.4+mc1.21.1.jar": "client",
+  "sodium-neoforge-0.8.13+mc1.21.1.jar": "client",
   "solcarrot-1.21.1-1.16.6.jar": "both",
   "sophisticatedbackpacks-1.21.1-3.25.55.1852.jar": "both",
   "sophisticatedbackpackscreateintegration-1.21.1-0.1.6.99.jar": "both",
@@ -173,7 +176,7 @@
   "stattweaks-neoforge-v2.0.0.jar": "both",
   "supermartijn642configlib-1.1.8-neoforge-mc1.21.jar": "both",
   "supermartijn642corelib-1.1.21-neoforge-mc1.21.jar": "both",
-  "supplementaries-1.21-3.5.26-neoforge.jar": "both",
+  "supplementaries-neoforge-1.21.1-3.7.7.jar": "both",
   "tagtooltips-neoforge-1.21.1-1.2.0.jar": "client",
   "titanium-1.21-4.0.43.jar": "both",
   "toolsjs-0.1.1.jar": "both",

plan/10-uptime-kuma.md

@@ -5,13 +5,13 @@
 > card. Both ping `minecraft` over `mcnet` but serve different purposes.
 
 Status monitoring + public status page. Service `uptime-kuma`
-(`louislam/uptime-kuma:1`), web UI on `:3001`, reached only through caddy at
+(`louislam/uptime-kuma:2`), web UI on `:3001`, reached only through caddy at
 `https://status.${BASE_DOMAIN}`. Joined to `mcnet`, so it can probe every other
 service by its internal container name.
 
 ## Add a Minecraft monitor
 
-Uptime Kuma 1.x ships a built-in **Minecraft Server** monitor type. It uses the
+Uptime Kuma ships a built-in **Minecraft Server** monitor type. It uses the
 Server List Ping protocol (the same ping the vanilla multiplayer list uses):
 unauthenticated, so it works fine with `ONLINE_MODE=FALSE` /
 `ENFORCE_SECURE_PROFILE=FALSE`. It reports latency, online/max players, and MOTD.
@@ -53,6 +53,12 @@ monitor stays green. Run both to tell *server down* apart from *path broken*.
   `https://auth.${BASE_DOMAIN}`, `https://distribution.${BASE_DOMAIN}`,
   `https://${BASE_DOMAIN}`, `https://files.${BASE_DOMAIN}` — a red
   `distribution.` here explains client mod-mismatch join failures.
+- **1 → 2 upgrade (2026-10-25)** — moved off `:1`, whose image runs Node 18
+  (EOL, no fix for the Oct 2026 Node CVEs). The first `:2` start migrates
+  `kuma.db` in place (one-way, minutes on a ~140M DB; status page down until it
+  finishes — don't interrupt). Per host: `docker compose stop uptime-kuma`, tar
+  the `kuma_data` volume into `./backups/`, then `pull` + `up -d uptime-kuma`.
+  Rollback = restore the tarball + revert the tag to `:1`.
 
 > **An HTTP monitor cannot see an SPA break.** It asserts "the server returned
 > 200", which is a much weaker claim than "the app works". `files.` (Filestash)