fix(ci): resolve MinIO images from quay.io after the Docker Hub withdrawal

CHANGELOG.md

@@ -75,6 +75,20 @@ The project publishes 0.x prerelease versions; a stable release line is not yet
 
 ### Fixed
 
+- Every MinIO image reference in the test stack, the local development stack and
+  the self-hosted single-node Compose profile now resolves from `quay.io` instead
+  of Docker Hub. MinIO stopped publishing container images in October 2025 and
+  removed the `minio/minio` and `minio/mc` repositories from Docker Hub, so an
+  anonymous `docker compose up` fails with `pull access denied for minio/minio,
+  repository does not exist or may require 'docker login'`. Because `Validate
+  Agent memory` → `HTTP, CLI and MCP lifecycle` is a required status context,
+  that registry withdrawal blocked every pull request from merging (`#207`).
+  `quay.io` still serves the exact digests pinned in `docker-compose.test.yml`,
+  so no image bytes change: the digest-pinned test stack keeps its digests and
+  the release-tagged deployment stack keeps its tags — only the registry host
+  differs. `deploy/compose/compose.yaml` previously carried the same broken
+  reference, so the documented self-hosted path would have failed on a cold
+  host even though no workflow exercises it.
 - A configured URL that carries credentials in a shape `url.Parse` does not
   report as userinfo no longer reaches output. `admin:pw@host` parses as
   `Scheme="admin"` with the credential in `Opaque` and `User` unset, so an

deploy/compose/compose.yaml

@@ -90,7 +90,9 @@ services:
       start_period: 5s
 
   minio:
-    image: minio/minio:RELEASE.2025-04-22T22-12-26Z
+    # MinIO withdrew its Docker Hub repositories in October 2025; quay.io serves
+    # the same release tags.
+    image: quay.io/minio/minio:RELEASE.2025-04-22T22-12-26Z
     restart: unless-stopped
     command: server /data --console-address :9001
     environment:
@@ -108,7 +110,7 @@ services:
       start_period: 10s
 
   minio-init:
-    image: minio/mc:RELEASE.2025-04-16T18-13-26Z
+    image: quay.io/minio/mc:RELEASE.2025-04-16T18-13-26Z
     restart: "no"
     depends_on:
       minio:
@@ -217,7 +219,7 @@ services:
       start_period: 10s
 
   minio-client:
-    image: minio/mc:RELEASE.2025-04-16T18-13-26Z
+    image: quay.io/minio/mc:RELEASE.2025-04-16T18-13-26Z
     profiles: ["tools"]
     environment:
       MEM_S3_BUCKET: ${MEM_S3_BUCKET:-mem}

docker-compose.test.yml

@@ -22,7 +22,9 @@ services:
 
   minio:
     profiles: ["e2e"]
-    image: minio/minio:latest@sha256:14cea493d9a34af32f524e538b8346cf79f3321eff8e708c1e2960462bd8936e
+    # MinIO withdrew its Docker Hub repositories in October 2025; quay.io serves
+    # the same digest-pinned image.
+    image: quay.io/minio/minio:latest@sha256:14cea493d9a34af32f524e538b8346cf79f3321eff8e708c1e2960462bd8936e
     command: server /data --console-address ":9001"
     environment:
       MINIO_ROOT_USER: mem
@@ -40,7 +42,7 @@ services:
 
   minio-init:
     profiles: ["e2e"]
-    image: minio/mc:latest@sha256:a7fe349ef4bd8521fb8497f55c6042871b2ae640607cf99d9bede5e9bdf11727
+    image: quay.io/minio/mc:latest@sha256:a7fe349ef4bd8521fb8497f55c6042871b2ae640607cf99d9bede5e9bdf11727
     depends_on:
       minio:
         condition: service_healthy

docker-compose.yml

@@ -40,7 +40,9 @@ services:
       retries: 10
 
   minio:
-    image: minio/minio:latest
+    # MinIO withdrew its Docker Hub repositories in October 2025; quay.io serves
+    # the same image.
+    image: quay.io/minio/minio:latest
     container_name: mem-minio
     restart: unless-stopped
     command: server /data --console-address ":9001"
@@ -60,7 +62,7 @@ services:
 
   # Bootstrap: create default bucket
   minio-init:
-    image: minio/mc:latest
+    image: quay.io/minio/mc:latest
     depends_on:
       minio:
         condition: service_healthy