#306: admin Save no longer wipes peeringEnabled — saveSettings merges over serverSettings #307

Merged
Cordy merged 3 commits from fix/set62 into main 2026-08-21 17:01:42 +00:00
Owner

Fixes the "peering turns off after redeployment" dogfood finding: the trigger was any admin Save, not the redeploy. saveSettings sent a hand-built partial object to PUT /api/v1/settings (replace semantics), zeroing peeringEnabled, peeringExpandGroups, peeringMaxFileBytes, peeringBaseUrl. Now it merges its form fields over serverSettings — the same pattern the peering toggle already used — so all non-form fields (present and future) survive.

Full diagnosis on #306. Frontend-only.

Fixes the "peering turns off after redeployment" dogfood finding: the trigger was any admin **Save**, not the redeploy. `saveSettings` sent a hand-built partial object to `PUT /api/v1/settings` (replace semantics), zeroing `peeringEnabled`, `peeringExpandGroups`, `peeringMaxFileBytes`, `peeringBaseUrl`. Now it merges its form fields over `serverSettings` — the same pattern the peering toggle already used — so all non-form fields (present and future) survive. Full diagnosis on #306. Frontend-only.
Cordy merged commit 9efcce43d5 into main 2026-08-21 17:01:42 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#307
No description provided.