diff --git a/Release-Notes/v2026.11.md b/Release-Notes/v2026.11.md index abc76ef..3c6c188 100644 --- a/Release-Notes/v2026.11.md +++ b/Release-Notes/v2026.11.md @@ -72,6 +72,17 @@ Tested on an isolated copy of the stack (compose project `hstest`, its own volum - **Take a fresh DB backup right before deploying.** On first start mysql 8.4.13 upgrades the data dictionary in place (about 1 minute; the healthcheck's 180s `start_period` covers it). MySQL can't be downgraded in place, so going back to 8.4.11 means restoring the backup into a fresh volume. - `docker compose pull db && docker compose up -d --build`. No env var, volume or permission changes. +### Production deploy — 2026-11-16 +Deployed with `docker compose pull db && docker compose up -d --build`. A fresh backup was taken right before: `~/backups/homeschool/homeschool-20261116-2352-pre-v2026.11-deploy.sql.gz` (18,286 bytes, verified). +- All three containers are healthy. Running versions: mysql 8.4.13, Python 3.12.16, fastapi 0.163.1, starlette 1.10.0, SQLAlchemy 2.1.9, nginx 1.30.6. +- MySQL upgraded in place, `80411` → `80413`, in about 1 minute with no errors. Row counts match the pre-deploy backup (3 users, 3 children, 72 sessions, 1,158 timer events), and `CHECK TABLE` is OK on users, children, sessions, timer_events and schedule_blocks. +- Through https://homeschool.chns.tech: + - `/`, `/login` and `/api/health` return 200, and the served bundle matches the new build. + - Protected routes without a token return 401. + - A real child's TV dashboard loads, and its WebSocket connects over `wss://`. +- Real user traffic after the deploy returned 200s. The backend log shows no errors. +- Prod checks were read-only. Registering and admin login fire ntfy alerts, so the write paths were covered by the test-stack runs above. + ### Rollback - Git tag: `pre-update-2026-11-16` - Image tags: `homeschool-backend:pre-update-2026-11-16`, `homeschool-frontend:pre-update-2026-11-16`, `mysql:8.4.11-pre-update-2026-11-16` @@ -83,4 +94,4 @@ Tested on an isolated copy of the stack (compose project `hstest`, its own volum docker exec -i homeschool_db sh -c 'exec mysql -uroot -p"$MYSQL_ROOT_PASSWORD"' docker compose start backend frontend ``` - To return to mysql 8.4.11 after the 8.4.13 upgrade, recreate the volume first: stop the stack, remove or rename `homeschool_mysql_data`, set the image back to `mysql:8.4.11`, `docker compose up -d db`, wait until it's healthy, then run the restore above. + For a production restore, prefer the newer pre-deploy backup (`homeschool-20261116-2352-pre-v2026.11-deploy.sql.gz`), which is in the same format. To return to mysql 8.4.11 after the 8.4.13 upgrade, recreate the volume first: stop the stack, remove or rename `homeschool_mysql_data`, set the image back to `mysql:8.4.11`, `docker compose up -d db`, wait until it's healthy, then run the restore above.