bvandeusenandClaude Opus 5.5
6028d78844
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>
9 lines
451 B
SQL
9 lines
451 B
SQL
-- Additive: records when Lidarr accepted the add (POST artist/album)
|
|
-- for an approved request. NULL = not yet sent/confirmed; the
|
|
-- reconciler idempotently (re)sends the add until this is set, then
|
|
-- watches for the import. Decouples the durable admin approval from the
|
|
-- best-effort Lidarr call, so a transient Lidarr outage does not force a
|
|
-- manual re-approve.
|
|
ALTER TABLE lidarr_requests
|
|
ADD COLUMN lidarr_add_confirmed_at timestamptz;
|