Release 1.72.1
Release Notes - Seatmap Platform
Version 1.72.1 - 2026-08-31
Release Focus: Background tiles are generated from the rendered venue image, so regenerating an organisation’s backgrounds runs within the converter’s memory budget. Delivered as a patch on top of the 1.72 line.
What’s Fixed
Background tiles are generated from the rendered image
A venue background larger than a single tile is rendered one tile at a time. Those tiles are now stored directly rather than being reassembled and split apart again, so generating a tiled background for a large venue takes less memory and less time. Regenerating every background in an organisation runs within the converter’s memory budget.
Tile geometry, file naming and grid metadata are unchanged. Existing tiled backgrounds stay valid, no cached tile URL changes, and no background needs to be regenerated to benefit — the saving applies the next time each one is generated.
Issue: SEAT-1223.
Conversion results report failures instead of reporting success
Two changes to the /background response that an integrator reading it directly should know about:
- A conversion whose full, preview or blurred image did not generate now returns
status: "error". It previously returnedstatus: "success"with the failure recorded only on the individual image. - A tile set that could not be generated is now reported as
tileswith an error status, rather than being left out of the response.
Callers that branch on the top-level status will see failures they did not see before. Callers that test for the presence of tiles should check its status rather than treating presence as success. The renderer already does both, so no client update is required.
Affected products
converter-service— background tiles encoded from the rendered image, with the previous behaviour retained as a fallback; conversion results report failed image variants and failed tile sets.
Upgrade
No API or database changes, and no action is required. The new behaviour applies on upgrade.