# v0.2.5 (2026-04-22)

Hotfix release on top of v0.2.4 — the settings page couldn't save numeric
fields after the cache-TTL / max-entries rework. See v0.2.4 notes for the
main changes (thumbhash-validated cache, settings UX overhaul, mobile-nav
parity).

## Bug Fixes

- **Accept numeric values in settings update payload** — Svelte's `bind:value` on `<input type="number">` coerces to a JS number, and Pydantic v2 wouldn't auto-coerce `int → str`, producing a 422 on every save that touched a numeric setting (TTL, max entries) after v0.2.4. Widened numeric fields to `int | str | None` in `SettingsUpdate` and normalized to `str` before persisting. ([d7d0a5d](https://git.dolgolyov-family.by/alexei.dolgolyov/notify-bridge/commit/d7d0a5d))

---

<details>
<summary>All Commits</summary>

- [d7d0a5d](https://git.dolgolyov-family.by/alexei.dolgolyov/notify-bridge/commit/d7d0a5d) — fix(settings): accept numeric values in update payload *(alexei.dolgolyov)*

</details>