Skip to content

ensure pip is actually upgraded during Docker build#2871

Open
ankit1w wants to merge 1 commit intosherlock-project:masterfrom
ankit1w:patch-1
Open

ensure pip is actually upgraded during Docker build#2871
ankit1w wants to merge 1 commit intosherlock-project:masterfrom
ankit1w:patch-1

Conversation

@ankit1w
Copy link
Copy Markdown

@ankit1w ankit1w commented Apr 4, 2026

Previously, pip was upgraded in an isolated AS build stage that was never copied into the final image, meaning the upgrade was completely discarded. This commit removes the unused multi-stage block and moves the pip upgrade into the final stage. This ensures the container actually uses the latest version of pip when installing the project dependencies, while also cleaning up dead code.

Previously, pip was upgraded in an isolated AS build stage that was never copied into the final image, meaning the upgrade was completely discarded. This commit removes the unused multi-stage block and moves the pip upgrade into the final stage. This ensures the container actually uses the latest version of pip when installing the project dependencies, while also cleaning up dead code.
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