v2026.8.4

Fixes a regression in v2026.8.3. If you are on v2026.8.3, update: editing or creating a zone from the panel silently does nothing on that version.

Fixed

Every zone save from the panel failed (#813, #812). v2026.8.3 added a precipitation_superseded field to the zone, used to keep rain from being counted twice around a bucket reset, but did not add it to the write schema of the zones endpoint. The panel reads a zone and posts the whole object back when you edit any single field, and the endpoint rejects unknown keys, so the whole save was refused with a 400 whatever you were actually editing. Changes appeared to be accepted and were silently dropped.

Nothing was lost or corrupted by this: the saves never happened, so a zone edited on v2026.8.3 still holds the values it had before. Re-apply those edits after updating.

There is now a test comparing the fields a zone is made of against the keys the endpoint accepts, which fails on exactly this. It should have existed before that field was added.

Thanks to @PrincepsCivitatis for a report that pinpointed the key, the endpoint, the failing request and the workaround, and to @Lokilicious for the first sighting.

Full Changelog: v2026.8.3...v2026.8.4