v1.1.2

If you are running 1.1.1, upgrade. 1.1.1 renders a blank page and the UI is completely unusable. This release fixes it and contains nothing else of substance.

Fixes

1.1.1 rendered a blank page (#135)

react was bumped to 19.2.8 in 1.1.1 while react-dom stayed behind at 19.2.7. React 19 refuses to run with a version skew between the two packages, so createRoot threw before anything mounted:

Uncaught Error: Minified React error #527
  → "Incompatible React versions: react 19.2.8 / react-dom 19.2.7"

Nothing catches that — there is no error boundary above ReactDOM.createRoot — so #root stayed empty and every page was white.

The backend was never affected. In 1.1.1 the API, the inbox poller, cron jobs and document analysis all kept working normally; /, the JS and the CSS all returned 200. Only the browser-side mount failed, so no data was lost or mis-processed while you were on 1.1.1 — you just could not see or drive any of it from the UI.

Both packages now resolve to 19.2.8.

Upgrade note: none — pull the image and restart. If the page is still blank afterwards, you are being served a cached index.html pointing at the old bundle hash; hard-reload once (Cmd/Ctrl-Shift-R).

Why CI did not catch this

tsc, eslint, check:i18n and vite build all pass on a react/react-dom skew — the failure only exists at runtime in a browser, which nothing in the pipeline exercised. Worth keeping in mind when reviewing future Dependabot bumps that touch a paired package: react and react-dom must always be bumped together.

Maintenance

• Bumped the transitive dev dependency brace-expansion 5.0.7 → 5.0.8 to clear GHSA-mh99-v99m-4gvg (high, DoS via unbounded expansion). Dev-only — it reached the tree through eslint → minimatch and was never shipped in the runtime image. The frontend CI job gates on npm audit --audit-level=low, so this advisory had already turned that job red on 1.1.1.
• Synced the stale version field in frontend/package-lock.json, which the 1.1.1 bump missed.

Full Changelog: v1.1.1...v1.1.2