Release 1.65.9
Release Notes - Seatmap Platform
Version 1.65.9 - 2026-05-08
Release Focus: Map ObjectOptimisticLockingFailureException to HTTP 409 across editor-service so concurrent writes against the same row return a stable retry signal instead of a 500.
What’s Fixed
Optimistic-locking conflicts return 409
When two clients write the same row concurrently, Hibernate raises ObjectOptimisticLockingFailureException. Editor-service previously let this escape as a generic 500, which integrators retried indiscriminately and incident response treated as a real outage. The exception now maps to 409 Conflict via @ResponseStatus, giving clients a documented signal to re-fetch and retry. Issue: SEAT-985.
Why it matters
409 Conflict is the standard HTTP semantic for “your write lost a race; please refresh and try again”. Clients can now implement a focused refetch+retry on 409 instead of broad retry-on-5xx that compounds load on every conflict.
Affected products
editor-service— exception mapping only.
Upgrade
Drop-in patch release. No API contract changes; previously-500 responses for optimistic-lock conflicts are now 409.