build: track devcontainer images via dependabot#168
Merged
Conversation
TheDZhon
previously approved these changes
Jun 17, 2026
TheDZhon
approved these changes
Jun 17, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the devcontainer build to pin and track both the devcontainer base image and the uv binary via Docker FROM lines, enabling Dependabot’s Docker ecosystem updates and removing duplicated UV_VERSION pinning across config/workflows.
Changes:
- Add a Dependabot
dockerecosystem entry for/.devcontainerto track DockerFROMimage references. - Switch
.devcontainer/Dockerfilefrompip install uv==...to copyinguv/uvxfrom Astral’s officialuvimage (pinned by digest). - Remove
UV_VERSIONpropagation fromregression.ymlanddevcontainer.jsonsince it’s now pinned in the Dockerfile.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/regression.yml | Removes UV_VERSION env/build-arg usage so CI builds rely on the Dockerfile-pinned uv stage. |
| .github/dependabot.yml | Adds Docker ecosystem scanning for /.devcontainer to keep devcontainer image references updated. |
| .devcontainer/Dockerfile | Introduces a dedicated uv stage pinned by digest and copies the binaries into the final devcontainer image. |
| .devcontainer/devcontainer.json | Removes build args for base image / UV_VERSION, relying on Dockerfile pinning instead. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Follow-up to #165.
What and why
dependabot.yml(directory: /.devcontainer) tracks both devcontainer images. Dependabot's Docker parser reads version references only from literalFROMlines, so both the base image (mcr.microsoft.com/devcontainers/python:3.11) and the uv image sit on their ownFROMline. The base image builds and runs inregression.yml, inside the trusted verification path.FROM … AS uvstage;COPY --from=uvthen lifts the/uvand/uvxbinaries. This replacespip install uv==…and pins the uv version in one place (Dockerfile) instead of three (Dockerfile,devcontainer.json,regression.yml).Both bullets close the open follow-ups from the #165 review: the docker block and the
UV_VERSIONdrift.uv image safety
@sha256:10902f…), like the base image. That beats the oldpip install uv==…running without--require-hashes.COPY --from=uvcopies only the static/uvand/uvxbinaries; the source image's OS layers stay out of the runtime.gh attestation verify oci://ghcr.io/astral-sh/uv:0.10.9 --owner astral-sh.