Repository navigation
fix: align Docker npm pin with release version - #55
Draft
cloudgpuapp wants to merge 3 commits into
Draft
cloudgpuapp wants to merge 3 commits into
cloudgpuapp wants to merge 3 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:8311b835a8e8ac3ca96e3274b4c7ab684eaf5c00has the identical tree to this head.Existing action pins and
contents: readpermissions 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.