release / govulncheck (push) Successful in 17s
release / web (push) Successful in 1m33s
release / go (push) Successful in 1m49s
release / integration (push) Successful in 5m42s
release / android (push) Successful in 5m59s
release / Build signed APK (releases and dev) (push) Successful in 6m9s
release / Attach APK to the Release (tag releases only) (push) Skipped
release / Build + push container image (push) Successful in 16s
release / Verify release artifacts (tag releases only) (push) Skipped
Applies rule 32's migration exception: each header still says what the schema was, what changes and what it prevents, but task, milestone, decision and rule ids are replaced by the practice they stood for, the operator quotes by the decision, single-install counts are dropped, and pointers to a deleted package and an external design doc are gone. golang-migrate keeps no checksum, so editing applied migrations' comments is safe. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
12 lines
703 B
SQL
12 lines
703 B
SQL
-- 0094_duplicate_distinct.up.sql — duplicates settle themselves, without
|
|
-- waiting on an admin.
|
|
--
|
|
-- distinct: one album holds two versions of a song that sound alike ("Lovesick"
|
|
-- and "Lovesick (Instrumental)"). They are not duplicates, and the resolver
|
|
-- dismisses them itself. mismatch now also covers one album holding the same
|
|
-- audio in several track slots, the resolver's wrong-file case.
|
|
-- The new value swaps the constraint in the same migration.
|
|
ALTER TABLE duplicate_groups DROP CONSTRAINT duplicate_groups_class_check;
|
|
ALTER TABLE duplicate_groups ADD CONSTRAINT duplicate_groups_class_check
|
|
CHECK (class IN ('same_release', 'cross_release', 'mismatch', 'distinct', 'review'));
|