|
| 1 | +# ExcaliDash v0.4.19 |
| 2 | + |
1 | 3 | Release date: 2026-02-17 |
2 | | -update release workflow, fix import tests |
| 4 | + |
| 5 | +## Highlights |
| 6 | + |
| 7 | +- New authentication platform across backend and frontend, including local accounts, optional OIDC integration, admin roles, and onboarding controls. |
| 8 | +- New password-reset flow and bootstrap setup code for first-admin initialization. |
| 9 | +- User identity, impersonation, and per-user isolation improvements in editor/dashboard flows. |
| 10 | +- Expanded import/export surface with compatibility support for legacy SQLite backups. |
| 11 | + |
| 12 | +## Upgrading |
| 13 | + |
| 14 | +<details> |
| 15 | +<summary>Show upgrade steps</summary> |
| 16 | + |
| 17 | +### Data safety checklist |
| 18 | + |
| 19 | +- Back up backend volume (`dev.db`, secrets) before upgrading. |
| 20 | +- Let migrations run on startup (`RUN_MIGRATIONS=true`) for normal deploys. |
| 21 | +- Run `docker compose -f docker-compose.prod.yml logs backend --tail=200` after rollout and verify startup/migration status. |
| 22 | + |
| 23 | +### Recommended upgrade (Docker Hub compose) |
| 24 | + |
| 25 | +```bash |
| 26 | +docker compose -f docker-compose.prod.yml pull |
| 27 | +docker compose -f docker-compose.prod.yml up -d |
| 28 | +``` |
| 29 | + |
| 30 | +### Pin images to this release (recommended for reproducible deploys) |
| 31 | + |
| 32 | +Edit `docker-compose.prod.yml` and pin the release tags: |
| 33 | + |
| 34 | +```yaml |
| 35 | +services: |
| 36 | + backend: |
| 37 | + image: zimengxiong/excalidash-backend:v0.4.19 |
| 38 | + frontend: |
| 39 | + image: zimengxiong/excalidash-frontend:v0.4.19 |
| 40 | +``` |
| 41 | +
|
| 42 | +Example: |
| 43 | +
|
| 44 | +```bash |
| 45 | +docker compose -f docker-compose.prod.yml up -d |
| 46 | +``` |
| 47 | + |
| 48 | +</details> |
| 49 | + |
| 50 | +## What's new |
| 51 | + |
| 52 | +- Backend auth stack |
| 53 | + - Added dedicated auth modules and routes (`backend/src/auth/*`) for login/register/refresh/me, account actions, admin controls, and OIDC callbacks. |
| 54 | + - Added auth middleware and mode-aware route protection. |
| 55 | + - Added auth mode configuration with `local | hybrid | oidc_enforced`. |
| 56 | + - Added system-level config, bootstrap setup code support, login-rate-limit configuration, and audit logging plumbing. |
| 57 | +- Security hardening |
| 58 | + - Added server- and client-side CSRF improvements and stability tests. |
| 59 | + - Added token hardening and refresh-token rotation controls. |
| 60 | + - Added trusted-proxy handling and stricter onboarding/session safety checks. |
| 61 | +- Data and collaboration improvements |
| 62 | + - Added import/export routes and services (including legacy migration/import compatibility). |
| 63 | + - Added drawings cache and socket authentication updates. |
| 64 | + - Added preview utilities and bug fixes for image-sync/persistence in collaborative editing. |
| 65 | +- Frontend auth + UX |
| 66 | + - Added login/register/profile/admin/setup/password-reset pages and onboarding flow components. |
| 67 | + - Added protected routes, auth context integration, identity sync, pagination/state hooks, and impersonation banner/update UI. |
| 68 | + - Updated dashboard and editor interactions for authenticated multi-user behavior. |
| 69 | +- Operations and DX |
| 70 | + - Added deployment/release tooling cleanup (`scripts/*`, compose updates, workflow refinements). |
| 71 | + - Added/updated migration and setup scripts for safer local workflows. |
| 72 | + - Expanded test coverage (backend, frontend, and e2e), including new auth and image/persistence cases. |
| 73 | + |
| 74 | +## Migration / upgrade notes |
| 75 | + |
| 76 | +- Database changes now include auth-related schema migrations and require migration execution as part of upgrade: |
| 77 | + - New users/auth identity models |
| 78 | + - Auth flags/state |
| 79 | + - Bootstrap setup tracking |
| 80 | +- New/updated production-relevant environment requirements were added in config and docs: |
| 81 | + - `AUTH_MODE`, `JWT_SECRET`, `TRUST_PROXY`, OIDC variables, bootstrap/retry limits, audit/release switches. |
| 82 | +- `JWT_SECRET` now has stricter validation in production (`.env.example` documents this explicitly). |
| 83 | +- On first-run / migration to authenticated mode, users may encounter onboarding/setup screens; follow the documented first-admin setup flow. |
| 84 | +- Read updated docs and deployment notes before deploying. |
0 commit comments