Hotfix v2026.05.15.1 — allow discovery-mix variants in playlists CHECK constraints #49
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hotfix for v2026.05.15.0 — system playlists fully broken in prod.
R3 added the five discovery-mix
system_variantvalues (deep_cuts, rediscover, new_for_you, on_this_day, first_listens) to producers/registry/queries/clients but not to theplaylists_kind_variant_consistent/playlists_seed_consistentCHECK constraints (whitelist last set in migration 0021).insertSystemPlaylistfor any new mix → SQLSTATE 23514, and becauseBuildSystemPlaylistsis one all-or-nothing transaction the first new-mix insert aborts the entire build — so For-You/Discover refresh 500s and the daily lazy build fails too.Migration
0028_discovery_mix_variantsdrops + re-adds both constraints with all five new seedless variants (mirrors the 0021 drop-and-readd pattern; Postgres has no ALTER CONSTRAINT for CHECK). CHECK-only — sqlc/dbq unaffected (regen produced no drift). Mobile client → 2026.5.15+7.Single commit. CI green on
dev. Tracked: Fable #433.Post-deploy verification:
/api/albums/{id}/coverlatency on a successful build — the 24–26 s seen in the failing-build logs was likely aborted-txn contention; if it persists now it's a separate issue (noted in #433).🤖 Generated with Claude Code