From 036720bcfb08907a2138c4e6b9b4cbd87134ddb0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Bombeck?= Date: Thu, 10 Sep 2026 09:09:26 +0200 Subject: [PATCH] docs(changelog): name the modules route's method and the profile refusal as they are The 1.38.15 entry said PUT where the record-settings route answers PATCH, and promised a rejectedFields field on the managed-profile edit that only the two profile routes carry; the edit refuses with a 422 and the issue list. --- CHANGELOG.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index b9f390c4c..7ba3240aa 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -13,10 +13,10 @@ on every surface, and four more journeys in the gate. can derive from it. Both arms require the fresh second factor the create and delete routes already do, refuse with 404 rather than 403 for a record the caller does not manage, and the edit is capped at ten an hour per - account. Every field is documented; `rejectedFields` says which value the - server would not take. + account. Every field is documented; a value the server will not take is a + 422 with the issue list. -- **Modules are switched per record.** `GET`/`PUT /api/record-settings/modules` +- **Modules are switched per record.** `GET`/`PATCH /api/record-settings/modules` read and write the module map of the record the browser is acting on, and `GET /api/auth/me` under an active switch reports `modules` and `cycleTrackingEnabled` for that record, not for the caller. Navigation