Say which modules wait for a person's push, and announce the files a merge deleted (hq ADR 0236)

With a gate on the first machine and a rollback after it, a module's build rolls out by default. The ones kept back say why: the network path a rollback could not cross, the providers every consumer on a machine drops with, and the stores holding the photos. A merge's deleted files are announced, so a module whose manifest went is forgotten rather than asked to build (the public-acme plan failure).
2026-10-06 18:39:13 +02:00
parent 7f99fb4a85
commit 1fd2914ae1
14 changed files with 61 additions and 5 deletions
@@ -1,6 +1,10 @@
 {
  "module": "minio",
  "version": "1",
+  "upgrade": {
+    "policy": "record",
+    "why": "holds the photos themselves (irreplaceable, kept by photos) for its consumers: a person takes each build, after a backup (hq ADR 0236)"
+  },
  "provides": [
    {
      "name": "s3-bucket",