Repository navigation
Commit 9879196
build(images): move the two Dockerfile build pins with the lock
cde3834 took build 1.6.0 in uv.lock and publish-pypi.yml but stopped
there, and test_demo_image_build_pins.py failed on main exactly as
designed: Dockerfile.api and deploy/hf-space/Dockerfile pin
`build==<the version uv.lock resolves>` because `python -m build
--no-isolation` makes that pin the builder that actually runs. A lock
bump that leaves them behind means the image builds its wheel with a
different -- and now yanked -- builder than CI resolves.
The miss was mine and mechanical: I grepped for the pin under .github/,
scripts/ and docs/ only, so the two Dockerfiles never showed up. The
ratchet is the reason this cost one red run instead of a divergence
nobody noticed.
Verified: test_demo_image_build_pins.py and test_publish_workflows.py
pass (10 passed), and all three tests that read uv.lock pass (32 passed).
No `build==1.5.1` remains anywhere in the tree.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018ybRVCaL1Lyd9d5kFTndh31 parent cde3834 commit 9879196
2 files changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
21 | 21 | | |
22 | 22 | | |
23 | 23 | | |
24 | | - | |
| 24 | + | |
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
32 | 32 | | |
33 | 33 | | |
34 | 34 | | |
35 | | - | |
| 35 | + | |
36 | 36 | | |
37 | 37 | | |
38 | 38 | | |
| |||
0 commit comments