- Frontend: vue 3.5.43, vite 8.3.4, @vitejs/plugin-vue 6.0.10, pinia 4.0.3 (+ @vue/devtools-api 8.2.1 peer), vue-router 5.4.0; npm audit 6 -> 0 - package.json "type": "module"; vite.config.js resolves @ via import.meta.url - Backend: fastapi 0.143.0, sqlalchemy 2.1.4, PyMySQL 1.2.3, aiomysql 0.3.2, uvicorn 0.54.0, httpx 0.28.1, pydantic 2.14.1, pydantic-settings 2.15.0, PyJWT 2.15.1, cryptography 50.0.2, email-validator 2.3.0 - Settings: class Config -> SettingsConfigDict (Pydantic V2 deprecation) - python 3.12.15-slim base image - Releases now tagged vYYYY.MM (README, Release-Notes/v2026.10.md) Co-Authored-By: Claude Opus 5.5 <[email protected]>
50 lines
3.9 KiB
Markdown
50 lines
3.9 KiB
Markdown
# v2026.10
|
|
|
|
## v2026.10 — 2026-10-12
|
|
|
|
Monthly dependency update for October 2026. It is the first release under calendar versioning (`vYYYY.MM`); the previous release was `v1.1.1`.
|
|
|
|
### Security
|
|
- **Frontend: 0 npm audit findings**, down from 6 (4 high, 2 moderate):
|
|
- vue 3.5.12 → **3.5.43**: fixes `@vue/server-renderer` XSS (GHSA-g2v6-rqmx-r4w6). The app renders client-side only, so the real exposure was low.
|
|
- `source-map-js` event-loop DoS (GHSA-68fv-2mgg-jv7q), fixed by the lockfile refresh.
|
|
- vite 5.4.21 → **8.3.4** / esbuild: fixes the dev-server advisory (GHSA-67mh-4wv8-2f99) that was accepted in v1.1.0. Vite 5 is no longer maintained.
|
|
- Backend: `pip-audit` reports no known vulnerabilities, before or after.
|
|
|
|
### Frontend (major upgrades)
|
|
- vite 5.4.21 → **8.3.4** (Rolldown-based), @vitejs/plugin-vue 5.1.4 → **6.0.10**
|
|
- pinia 2.2.4 → **4.0.3**. Pinia 4 requires `@vue/devtools-api` alongside it, so `@vue/devtools-api` 8.2.1 is now a direct dependency.
|
|
- vue-router 4.4.5 → **5.4.0**. Upstream lists no breaking changes for plain vue-router 4 users.
|
|
- vue 3.5.12 → 3.5.43; axios 1.20.0 was already current.
|
|
- `package.json` now sets `"type": "module"`, and `vite.config.js` resolves `@` via `import.meta.url` instead of `__dirname`. This removes Vite 8's warning about the CommonJS config loader, which a future Vite major will drop.
|
|
- Version `2026.10.0`.
|
|
|
|
### Backend
|
|
- fastapi 0.141.1 → 0.143.0, pydantic 2.13.5 → 2.14.1, pydantic-settings 2.5.2 → 2.15.0
|
|
- **sqlalchemy 2.0.35 → 2.1.4**, PyMySQL 1.1.2 → 1.2.3, aiomysql 0.3.0 → 0.3.2. PyMySQL 1.2.3 broke SQLAlchemy 2.0.35's connection ping in September; it works with 2.1.4.
|
|
- uvicorn 0.30.6 → 0.54.0, httpx 0.27.2 → 0.28.1, PyJWT 2.15.0 → 2.15.1, cryptography 50.0.1 → 50.0.2, email-validator 2.2.0 → 2.3.0
|
|
- `Settings` uses `model_config = SettingsConfigDict(...)` instead of the class-based `Config`. Pydantic deprecated the old form, and V3 will remove it.
|
|
- Unchanged (already current): starlette 1.7.0, anyio 4.15.1, bcrypt 5.0.0, alembic 1.20.0, Mako 1.4.3, python-multipart 0.0.32.
|
|
|
|
### Base images
|
|
- python 3.12.14-slim → **3.12.15-slim**
|
|
- node 24.21.0-alpine, nginx-unprivileged 1.30.5-alpine and mysql 8.4.11 were already the latest. The rebuild applies pending OS package updates (5 apt, 8 apk) through the existing `apt-get upgrade` / `apk upgrade` steps.
|
|
|
|
### Testing
|
|
Tested on an isolated copy of the stack (separate project, volume and port) with the 2026-10-12 production dump restored:
|
|
- API smoke test through nginx: 125/126 checks passed. It covered:
|
|
- auth (register, login, refresh, forged/`alg=none` JWT rejection)
|
|
- CRUD on children, subjects, options, schedules, blocks, routine, break activities and rules
|
|
- the full timer lifecycle, including break events, select/skip/reset, agenda and rules overlays
|
|
- WebSocket broadcast of all 16 events
|
|
- the TV dashboard with an active block
|
|
- every list GET route
|
|
- super-admin impersonation of all 3 real users, reading their real data and TV dashboards
|
|
|
|
The one failed check, refresh, was a test artifact: the `Secure` cookie isn't sent over plain HTTP. Refresh returns 200 when the cookie is sent.
|
|
- Headless Chromium against the built UI: login form, route guards, dashboard/logs/admin rendering, reload persistence, and the TV view showing the active block and staying live after a WebSocket event. The same test was also run against the previous image to tell regressions apart from existing behavior.
|
|
|
|
### Known / existing (not changed in this release)
|
|
- An expired session redirects to `/login` **without** the `?redirect=` query, so after signing in the user lands on `/dashboard` instead of the page they asked for. The axios interceptor (`useApi.js`) does a hard `window.location.href = '/login'` that overrides the router guard's redirect. The previous build behaves the same way.
|
|
- mysql:8.4.11 upstream image findings from v1.1.0 still apply until Oracle publishes a newer 8.4.x.
|