release / go (push) Successful in 2m6s
release / web (push) Successful in 1m15s
release / govulncheck (push) Successful in 19s
release / integration (push) Successful in 4m46s
release / android (push) Successful in 4m47s
release / Build signed APK (push) Successful in 5m38s
release / Attach APK to the Release (tag releases only) (push) Skipped
release / Build + push container image (push) Successful in 31s
release / Verify release artifacts (tag releases only) (push) Skipped
Reports, Duplicates and Suspect sources now end the same way: the file
goes and the track stays, marked missing with its likes, plays and
playlist places, until a good copy lands in the library and move
adoption or missing-pair folding brings it back.
- library.RemoveFile removes one track's file and marks the track
missing with the queue it was removed from and who removed it
(tracks.removed_reason / removed_by, migration 0104). The duplicate
resolver's wrong-slot removal shares the same marking.
- POST /api/admin/quarantine/{id}/remove-file removes a reported file,
clears the listeners' reports, marks open playback errors deleted and
records removed_file in the Reports history. A wrong-file or
wrong-tags report drops the file's recording MBID.
- POST /api/admin/library/suspect-sources/{id}/remove removes a video
rip's file and its MBID, and writes a suspect_file_remove audit row.
- The removal reason clears with the missing mark when a file returns.
Grimoire #7743 (milestone 635).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
10 lines
439 B
SQL
10 lines
439 B
SQL
-- Postgres cannot drop an enum value, so removed_file stays in
|
|
-- quarantine_action_kind; its history rows read as deleted_file again.
|
|
UPDATE quarantine_actions SET action = 'deleted_file' WHERE action = 'removed_file';
|
|
|
|
ALTER TABLE tracks
|
|
DROP CONSTRAINT IF EXISTS tracks_removed_only_missing,
|
|
DROP CONSTRAINT IF EXISTS tracks_removed_reason_check,
|
|
DROP COLUMN IF EXISTS removed_by,
|
|
DROP COLUMN IF EXISTS removed_reason;
|