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>
10 lines
586 B
SQL
10 lines
586 B
SQL
-- 0078_drop_duplicate_lidarr_state.up.sql — the duplicate resolver works
|
|
-- without Lidarr.
|
|
--
|
|
-- 0075 recorded Lidarr's view of each duplicate copy (tracked or unmapped)
|
|
-- because a copy Lidarr mapped could not be removed without Lidarr downloading
|
|
-- it again. Lidarr is gone: Minstrel is the only program writing the library,
|
|
-- so no copy is anyone else's to keep, and the column has nothing to say.
|
|
ALTER TABLE duplicate_group_members DROP CONSTRAINT IF EXISTS duplicate_group_members_lidarr_state_check;
|
|
ALTER TABLE duplicate_group_members DROP COLUMN IF EXISTS lidarr_state;
|