Files
computer-playbook/roles/svc-ai-mcp-adapter/meta/services.yml
kevinveenbirkenbachandClaude Opus 5 627ff73fae fix(svc-ai-mcp-adapter): put the docker-version suppressor where the check reads it
The marker sat above image:, and the check reads it relative to the version: key, either on that line or on the one directly above. Neither matched, so the role declared a pin and still drew an Outdated warning on every run. A warning does not fail the run, so the dead suppressor stayed invisible.

Negative control against the committed file: is_suppressed_at reports same-line=False and line-above=False at HEAD, True after the move. A repo-wide scan with the same helper finds no other version key whose suppressor fails to apply; the seven that looked misplaced use the same-line form, which is equally valid.

Moved rather than bumped: the marker's own reason is that this is the base of a self-built stdlib-only image, and svc-db-qdrant pins the identical 3.13.15-slim for the identical reason. Raising one would split the two adapters.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-08 22:38:49 +02:00

28 lines
514 B
YAML

---
mcp-adapter:
modes:
compose:
enabled: false
swarm:
enabled: false
bond: 1
enabled: true
shared: true
image: python
# nocheck: docker-version base of a self-built stdlib-only image, not the served application
version: "3.13.15-slim"
custom: true
name: mcp-adapter
min_storage: 130MB
cpus: "0.25"
mem_reservation: 24m
mem_limit: 48m
pids_limit: 64
healthcheck:
flavor: http_status
path: health
ports:
internal:
http: 8080
lifecycle: alpha