Repository navigation
build(docker): install runtime deps from uv.lock - #28
Merged
Merged
Conversation
The image installed the wheel with `uv pip install`, which resolved its dependencies fresh from PyPI and ignored uv.lock, so the image could ship package versions pip-audit never checked. Export the locked runtime deps with hashes in the build stage (`uv export --locked`, which fails the build on a stale lock) and install them with --require-hashes, then install the wheel with --no-deps. Pin the uv base image to 0.13.9-python3.13-trixie-slim for repeatable builds, and add the docker ecosystem to Dependabot so it bumps the pin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Redux Build System — CI Report
Overall: ✅ 7 passed · 0 failed · 2 skipped |
Trosper3
approved these changes
Nov 17, 2026
Trosper3
left a comment
There was a problem hiding this comment.
Thanks again for the good catch here. I will be looking at turning on a few settings across the other repos now thanks to you. :)
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.
Summary
The image installed the wheel with
uv pip install, which resolves runtime dependencies fresh from PyPI and ignoresuv.lock. Theauditgate checks the lock, so the image could ship versions pip-audit never saw. For example, it had scipy 1.18.1 while the lock had 1.18.0.uv export --locked --no-dev --no-emit-project. That writes the locked runtime deps with hashes, and--lockedfails the build ifuv.lockis out of date withpyproject.toml. (--frozenwould silently export the stale lock; I checked.)--require-hashes, then installs thequantumsolverwheel with--no-deps. The integration suite still tests the wheel.uv:python3.13-trixie-slimtag touv:0.13.9-python3.13-trixie-slim, which is what the floating tag resolves to today.dockerecosystem so it bumps that pin.Testing
uv export --lockedexactly. The one exception iscolorama, which the lock markssys_platform == 'win32', so Linux correctly skips it.pyproject.tomlwithout re-locking makesdocker buildfail at theuv export --lockedstep.Dependabot needs repository settings (admin)
.github/dependabot.ymlalready lists theuvecosystem, which coversuv.lock. But Dependabot has never opened a PR on this repo, even though several dependencies are behind (gunicorn 24.1.1 → 27.0.1, qiskit 2.4.1 → 2.6.2, qiskit-aer 0.17.2 → 0.18.4, ruff, pytest). The API reports Dependabot alerts are disabled, and the dependency graph appears to be off. Someone with admin access needs to enable these under Settings → Code security (they may be blocked at the org level, under ReduxISU's own Code security settings):uv.lock(e.g. werkzeug via Flask). Scheduled version updates normally bump only direct dependencies, so without this, transitive fixes depend on the pip-audit gate failing and someone re-locking by hand.🤖 Generated with Claude Code