- Shipped
- 15 ஆகஸ்ட், 2026 அன்று 5:54 AM UTC
- Author
- kamo
- Commit
- 3113fbe
"Save failed: Failed to save branding identity settings" discarded the status and body of a PUT that enforces the applied security model, so a 403 whose reason was "Alcohol-related content is not permitted by the applied security model" reached the user as a generic branding failure — unactionable for them, and nothing for a bug report to go on. Diagnosing it took a hand-made request against the service. Surfaces the status and the backend's own message, matching the colors PATCH immediately above, which has always done this.