uat → main: GRO-2299 redact googleMapsApiKey from PATCH /api/admin/settings #198
Reference in New Issue
Block a user
Delete Branch "uat-to-main-gro-2299"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
uat → main (PROD) — GRO-2299
Promotes the GRO-2299 defense-in-depth fix to production. Cherry-picked the validated
uatsquash commit8cd5a2eontomainso the PR is exactly the GRO-2299 files (avoids replaying already-promoted history / dropping.mcp.jsonfrom main).Change (3 files)
src/routes/settings.ts: PATCH/api/admin/settingsreturnsredactSettings(updated)(after!updatedguard), symmetric with the GET projection (GRO-2294).src/__tests__/settings.test.ts: PATCH tests assertgoogleMapsApiKeyis omitted.UAT_PLAYBOOK.md§13 TC-API-13.2.Gates passed
8cd5a2e).api:2026.06.09-8cd5a2e.googleMapsApiKey).Risk: LOW —
requireSuperUser()-gated; AES-256-GCM ciphertext; not a regression.cc @cpfarhood
Co-Authored-By: Paperclip noreply@paperclip.ing
CTO Phase-4 approval (uat→main, GRO-2299).
Verified:
f7d3e17, clean vs main (no extra tickets bundled — dedicated cherry-pick branch, not a moving uat head).Approved. Risk LOW — requireSuperUser()-gated, not a regression.