Release 1.73.4
Release Notes - Seatmap Platform
Version 1.73.4 - 2026-09-10
Release Focus: Deleting a price now clears the assignments that bind it to seats and areas, and refuses to run while any of those seats or areas is sold or held. Organisation and user administration act only within the caller’s own tenant and organisation, and two editor fixes restore the Save button after the first edit and make a long event list scrollable. Delivered as a patch on top of the 1.73 line.
What’s Fixed
Deleting a price clears its assignments
Deleting a price removes that price together with its assignments to seats and areas, in one transaction. The delete is refused with 409, and everything is left in place, while any of those seats is sold, held in a cart or withheld from sale, and while any of those areas has tickets held or has already sold tickets. A deleted price also releases its link to any pricing zone, so the zone can be deleted once no price is linked to it.
Creating, updating and deleting a price act only on prices that belong to the event in the request path, and a bulk create or update is applied in full or not at all. Updating or deleting a price that is not on that event answers 404, and a name already in use by another price on the same event answers 409.
Across the Booking API, a write that violates a uniqueness or referential constraint answers 409 with a problem detail naming the conflict.
Issue: SEAT-1271.
Organisation updates and deletes are scoped to the authenticated tenant
Updating or deleting an organisation through the tenant management API acts only on organisations that belong to the authenticated tenant. Deleting answers 204 only when an organisation in the caller’s own tenant was removed, and every other id answers 404; updating answers 404 on the same terms.
The tenant that owns an organisation is fixed when the organisation is created. A successful update responds with the organisation as stored, and the organisation endpoints report the stored values of the autologin and append-domain-to-login flags.
Issue: SEAT-1265.
User administration is scoped to the caller’s organisation
User administration in the organisation-users modal acts on members of the caller’s own organisation. The modal edits first and last name; a password is set from the account administration screens, which are open to global and tenant administrators. A user id outside the caller’s scope answers 404.
Removing a user from an organisation ends that membership and leaves their account on any other organisation intact. Adding an email address that already belongs to another organisation is refused; an address with no organisation of its own is attached to the caller’s organisation. Disabling an account that spans more than one organisation, or more than one tenant, is reserved for global administrators.
When a request is rejected, the reason is shown inline in the modal.
Issue: SEAT-1264.
The first shape edit after opening a schema enables Save
The first shape change made after opening a schema marks the schema as dirty, enables the Save button and triggers the unsaved-changes warning. Every subsequent edit continues to behave the same way. A single-edit change, for example adjusting a section fill and saving it, persists without needing a second unrelated edit to unlock the save flow.
Issue: SEAT-1261.
The schema Events list scrolls when it is long
The event list inside the schema Events modal scrolls inside the modal when it is longer than the viewport. Every event stays reachable no matter how many the schema has.
Issue: SEAT-1262.
Affected products
booking-service— price deletion clears seat and area assignments and refuses while any are sold or held; price and organisation writes are scoped to the event and the tenant in the request; constraint violations answer 409.editor-service— organisation user administration is scoped to the caller’s organisation, and account-wide changes are reserved for the roles that own them.editor-client— the organisation-users modal edits names and shows a rejection inline; the first shape edit after a load enables Save; the schema Events list scrolls.
Upgrade
No database changes, and no action is required. The new behaviour applies on upgrade.
A Booking API client that treats every non-2xx response as a transport failure needs branches for 404 and 409 on the price and organisation endpoints before it upgrades.