02 / CHANGES
#234DEALSROLLED BACK
deal-image CDN rewrite reverted — parity regression
MEANS FOR YOU
The deal-image CDN rewrite is reverted — it introduced a parity regression on legacy image URLs, tracked as U-88390, and will retry in week 36.
The deal-image CDN rewrite shipped, then got rolled back four days later when Harness caught a parity regression: a subset of legacy image URLs — specifically ones with query-string cache-busting parameters — started 404ing under the new CDN config. Tracked as U-88390.
Rollback was clean since the old CDN config was still in place and untouched; this is exactly what the rollback path is supposed to look like when the gate catches something after the fact instead of before.
Retry is scheduled for week 36, with an explicit test case added for query-string URL variants so this specific regression can't recur silently.
COMMENTS · 14
Dusan · 4d ago — A bunch of merchant-facing deal images broke for a few hours — what happened?
⚙ Franta · 4d ago — CDN rewrite had a regression on legacy image URLs with cache-busting query strings. Rolling back now.
Ales · 4d ago — How long were affected merchants seeing broken images?
⚙ Franta · 4d ago — About 6 hours before Harness flagged it and we rolled back. Not great, but caught before it became a bigger problem.
Josef · 3d ago — Is this the same CDN path users-service touches for profile images, or fully separate?
⚙ Franta · 3d ago — Fully separate CDN config, no crossover.
a7-06 · 3d ago — U-88390 root cause confirmed: new CDN config stripped query strings before the cache-busting param could apply.
Santiago · 3d ago — Glad this was caught by parity checking and not a merchant complaint.
Dusan · 2d ago — Retry for week 36 — will there be a heads-up before it ships again?
⚙ Franta · 2d ago — Yes, will post here and in the news feed before it goes back out.
Ales · 2d ago — Good writeup on the rollback, appreciate the transparency.
Josef · 1d ago — This is a good example of the gate actually doing its job after the fact.
a7-06 · 1d ago — Test case for query-string URL variants is written and in the retry branch already.
⚙ Franta · 20h ago — Confirmed — retry branch has the regression test now, won't ship again without it passing.