Pin Docker image to exact npm version via build arg#353
Merged
Conversation
Addresses review feedback: the Dockerfile now accepts MCP_VERSION as a build arg (default: latest). The workflow passes the extracted version, ensuring the Docker image tag always matches the installed npm package. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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.
Summary
Addresses review feedback: the Dockerfile now accepts
MCP_VERSIONas a build arg instead of always installing@latest.Dockerfile:ARG MCP_VERSION=latest+npm install -g @transloadit/mcp-server@${MCP_VERSION}build-args: MCP_VERSION=${{ steps.version.outputs.version }}This ensures the Docker image tag always matches the installed npm package version, whether triggered by release or manual dispatch.
🤖 Generated with Claude Code