v0.4.5 — Hotfix: Fixed expense UUID crash on HTTP
What's Changed
Fixed
- Profile page: adding a fixed expense no longer throws
TypeError: crypto.randomUUID is not a functionwhen the app is accessed over plain HTTP (common in self-hosted LAN setups)
Root cause: ProfileView was calling crypto.randomUUID() directly. This API is restricted to secure contexts (HTTPS or localhost). The existing generateUUID() utility in frontend/src/utils/uuid.ts already handles this with a Math.random-based fallback — the component just wasn't using it.
Fix: Replaced the direct call with generateUUID(). No behaviour change in HTTPS deployments.
Upgrading
No database migrations required. Drop-in upgrade from v0.4.4.
Full Changelog: v0.4.4...v0.4.5