# v2026.11 ## v2026.11 — 2026-11-16 Monthly dependency update for November 2026. It fixes one high-severity npm advisory, moves FastAPI forward 20 minor versions, and moves MySQL to 8.4.13 on the same 8.4 LTS line. No application code changes were needed. ### Security - **Frontend: 0 npm audit findings**, down from 1 high: - axios 1.20.0 → **1.21.1** pulls follow-redirects 1.16.3. That fixes GHSA-q3jh-wrc6-jgq8, GHSA-8r9p-f939-6h3c and GHSA-mrwp-f3q8-3g9p, where credential headers could leak on cross-origin redirects. They only affect axios's Node HTTP adapter, not the browser build, so the real exposure was low. - Backend: `pip-audit` reports no known vulnerabilities, before or after. - mysql 8.4.11 → 8.4.13 includes Oracle's quarterly patch releases. ### Updated | Component | From | To | Type | Notes | |---|---|---|---|---| | axios | 1.20.0 | 1.21.1 | minor | Security (follow-redirects) | | vue | 3.5.43 | 3.5.45 | patch | | | vite / @vitejs/plugin-vue | 8.3.4 / 6.0.10 | 8.3.8 / 6.0.11 | patch | | | pinia | 4.0.3 | 4.1.0 | minor | `@vue/devtools-api` 8.2.1 still satisfies its peer dependency | | vue-router | 5.4.0 | 5.5.1 | minor | | | fastapi | 0.143.0 | 0.163.1 | 0.x minor | See "Breaking changes reviewed" | | starlette | 1.7.0 | 1.10.0 | minor | Changes to form/multidict, GZip and TestClient; none of them used here | | pydantic / pydantic-settings | 2.14.1 / 2.15.0 | 2.14.3 / 2.16.3 | patch / minor | | | sqlalchemy | 2.1.4 | 2.1.9 | patch | | | anyio, alembic, PyMySQL | 4.15.1, 1.20.0, 1.2.3 | 4.16.0, 1.20.1, 1.2.4 | minor / patch | | | email-validator, python-multipart | 2.3.0, 0.0.32 | 2.4.0, 0.0.34 | minor / patch | | | python image | 3.12.15-slim | 3.12.16-slim | patch | | | node build image | 24.21.0-alpine | 24.22.3-alpine | minor | | | nginx-unprivileged | 1.30.5-alpine | 1.30.6-alpine | patch | Stays on the 1.30 stable branch | | mysql | 8.4.11 | 8.4.13 | patch (LTS) | The data dictionary upgrades in place on first start | Unchanged (already current): uvicorn 0.54.0, cryptography 50.0.2, PyJWT 2.15.1, bcrypt 5.0.0, httpx 0.28.1, aiomysql 0.3.2, Mako 1.4.3. Frontend `package.json` version is `2026.11.0`. ### Breaking changes reviewed (FastAPI 0.144–0.163) - 0.147/0.162 omitted form booleans, 0.149 empty form strings, 0.150 empty file inputs, 0.160 parameter-model `extra`: these only affect `Form`/`File`/parameter models. Not used here, since every endpoint takes JSON bodies. - 0.148: defaults for omitted parameters are no longer validated. This only affects `Query`/`Header`/`Cookie`/`Form`, none of which are used. - 0.151: an explicit JSON `null` is rejected for non-nullable fields, even when they have a default. Every field the frontend sends as `null` (log `session_id`/`subject_id`/`duration_minutes`, session `template_id`, block `label`/`duration_minutes`, child `birth_date`) is already typed `X | None`. The smoke test sends these nulls explicitly. - 0.145/0.155: `openapi_prefix` and `**extra` were removed from `FastAPI()` and the param functions. Neither is used. - 0.146: `root_path` is deprecated. Not used. - 0.162.6 drops Python 3.10. We run 3.12. ### Code changes - None. ### Deferred / skipped - **Python 3.12 → 3.13/3.14**: 3.12 still receives security fixes. A runtime minor jump needs its own run, with rebuilt compiled wheels (cryptography, pydantic-core, bcrypt) and a full regression pass. - **nginx 1.31.x**: this is the mainline branch. We stay on the 1.30 stable line. ### Verification Tested on an isolated copy of the stack (compose project `hstest`, its own volume, port 18054, ntfy disabled) with the 2026-11-16 production dump restored. Every unit was tested this way before it was committed. - **Container builds**: backend and frontend images build on every unit. `pip check` is clean, and `npm audit` reports 0 findings. - **API smoke test through nginx**: the pre-update images passed 106/106, and every update unit passed 96/96. The baseline count is higher only because its database still held one leftover test user. The test covers: - super-admin login and impersonation of all 3 real users, with every list GET and every schedule detail - register, login, wrong-password 401, forged-token 401, change-password and logout - create and update for children, strikes, subjects, options, templates, blocks, morning routine, break activities and rules - the full timer lifecycle: start, pause, resume, all 4 break events, select, complete, reset and skip - agenda, rules overlay show/hide, and WebSocket broadcast (15 events received) - the TV dashboard with an active block - activity logs with explicit `null` fields - **MySQL upgrade**: the test volume was created by 8.4.11 and then started on 8.4.13. The log shows `Server upgrade from '80411' to '80413' completed` after about 1 minute. `CHECK TABLE` returned OK, and the row counts were unchanged. - **Headless Chromium UI test**: passed 8/9 on both the new and the pre-update images. It checks: - the login guard redirect with its query string, the wrong-password error, and returning to the requested page - the dashboard, admin and logs pages via in-app navigation - the TV view showing the active block and staying live after WebSocket events The one failing check is identical on both builds and comes from the test itself: 401s from the pre-login refresh probe and the deliberate wrong password, plus WebSocket 429s from nginx's `tv_limit` (10 r/m). - There is no unit test suite or linter in this repo. ### Deploy notes - **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. ### 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` - Database backup: `~/backups/homeschool/homeschool-pre-update-2026-11-16.sql.gz` (18,279 bytes, taken before any changes, while 8.4.11 was running) - Restore command (it replaces the current tables; `--databases` dumps include `CREATE DATABASE` and `DROP TABLE`): ```bash docker compose stop backend frontend zcat ~/backups/homeschool/homeschool-pre-update-2026-11-16.sql.gz | \ 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.