Skip to content

fix: align Docker npm pin with release version - #55

Draft
cloudgpuapp wants to merge 3 commits into
mainfrom
codex/docker-pin-0.16.6-20261117
Draft

cloudgpuapp wants to merge 3 commits into
mainfrom
codex/docker-pin-0.16.6-20261117

Conversation

@cloudgpuapp

@cloudgpuapp cloudgpuapp commented Nov 17, 2026 •

Copy link
Copy Markdown
Collaborator

The root Dockerfile installs 0.15.0 while the package declares 0.16.6. This PR pins Docker to the already-published cloudgpu-mcp@0.16.6, adds a release-metadata assertion against future pin drift, and verifies the built image over stdio in an independent Ubuntu job.

The image job compares server version and complete tool objects/input schemas against an independently installed exact public npm release. Full and read-only containers run with --network none, a read-only root filesystem, empty temporary configuration and a dummy key. Only initialize/initialized/tools/list are sent. Timeouts bound execution; containers must exit with status 0 and are removed by cleanup.

Pre-release version-bump PRs are handled explicitly: image acceptance is skipped only when the exact-version endpoint returns HTTP 404 and a separate successful package-metadata response confirms that exact version is absent. The job summary then says no image build or smoke acceptance was performed. Network/timeout/auth/rate-limit/server errors, missing packages, malformed metadata and contradictory lookup results fail CI. Metadata consistency and unit tests remain mandatory. No automatic publication or release-trigger change.

Validation for head 507f31c9eef882158cf1f60d9015eff31dcee1d0:

  • Four reproducible availability tests cover published success, E404 + authoritative absence and explicit skip reporting, network/timeout/401/403/429/5xx errors, malformed responses and contradictory presence.
  • Full local npm suite: 150/150 pass; Python: 10/10 pass; script syntax, workflow YAML and whitespace checks pass. The stale Docker pin fails the unchanged pin-consistency assertion; the corrected pin passes.
  • Actual Ubuntu Docker job succeeded and did not skip the image step: it built 0.16.6, compared 59 full-mode and 34 read-only tools against published npm, and verified clean exits. The tested PR merge ref 8311b835a8e8ac3ca96e3274b4c7ab684eaf5c00 has the identical tree to this head.
  • Existing Node 20 verification job also succeeded in the same run.

Existing action pins and contents: read permissions are retained. No new third-party actions, custom secrets, registry login, image push, runtime-source changes or publishing metadata changes. Local Docker remains unavailable; real image acceptance ran in GitHub CI. This tests container startup, MCP interfaces and shutdown, not paid GPU or real-account service E2E.

This PR remains draft/unmerged. No tools/call, paid operation, merge, publication or release was performed. Docker Registry docker/mcp-registry#6472 is unchanged pending normal merge of this source fix.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant