Release 1.66.8

Release date: May 28, 2026

Release Notes - Seatmap Platform

Version 1.66.8 - 2026-05-28

Release Focus: Follow-up to the 1.66.6 autologin fix — pass editor 4xx responses through unchanged from booking-service, so clients see the editor’s real status code (e.g. 403 on invalid private key) instead of a synthetic 502.

What’s Fixed

Booking-service passes editor autologin 4xx responses through unchanged

After the SEAT-1019 trailing-slash fix in 1.66.6, the editor autologin endpoint correctly returned 403 Forbidden on an invalid private key. Booking-service’s EditorAutologinService, however, treated any upstream 4xx as a generic error and wrapped it as a 502 Bad Gateway to the client — eating the editor’s specific status and breaking integrators’ error-handling. Issue: SEAT-1019 follow-up.

What changed

The autologin proxy in booking-service now distinguishes upstream 4xx (a client-side problem with the request, e.g. invalid org key) from upstream 5xx (an actual editor outage). 4xx responses are surfaced to the caller with the editor’s original status code and structured body; only true 5xx situations remain mapped to 502 Bad Gateway.

Verification

Invalid org private-key UUID → booking returns 403 with the editor’s body (was 502).
Editor-service down → booking returns 502 (unchanged).
Valid request → 200 with login token (unchanged).

Affected products

booking-service — EditorAutologinService error mapping.

Upgrade

Drop-in patch release. Behavior change: integrators that previously coded around a 502 on invalid private keys will now see the editor’s real 403. The 403 is the documented and correct status; any client treating “all errors as 502” should pick up the canonical code.