build: add uv.lock for reproducible Docker builds#63
Conversation
|
Warning Review limit reached
Your plan currently allows 1 review/hour. Refill in 25 minutes and 36 seconds. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more review capacity refills, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
pip install -r requirements.txttouv sync --frozenwith a committed lockfilepyproject.tomlunder[project] dependenciesghcr.io/astral-sh/uv:0.11multi-stage pattern with deterministic installsrequirements.txt/requirements-worker.txtfor backward compatibility with local devWhy
Every
docker buildpreviously resolved dependency versions at build time, making builds non-reproducible. The lockfile pins exact versions so CI and production always get identical environments.Dependabot compatibility
Dependabot supports
uv.locknatively — it will open PRs updating bothpyproject.tomlbounds and lockfile pins.Test plan
DockerfileandDockerfile.workeruv lock --checkconfirms lockfile is in sync with pyproject.toml