Skip to content

chore: let uv 0.12 build with its built-in backend - #33

Merged
vinismarques merged 1 commit into
mainfrom
chore/uv-0.12
Aug 5, 2026
Merged

chore: let uv 0.12 build with its built-in backend#33
vinismarques merged 1 commit into
mainfrom
chore/uv-0.12

Conversation

@vinismarques

Copy link
Copy Markdown
Member

Building this package with uv 0.12.x printed:

warning: `build_system.requires = ["uv-build>=0.11.25,<0.12"]` does not contain the current uv version 0.12.1

When its own version falls outside the declared range, uv can't use the uv_build backend compiled into the binary and falls back to an isolated PEP 517 build that downloads the backend from PyPI. Scaffolded workers install maestro-worker-python from a GitHub source tarball, so that fallback ran on every worker image build.

  • Widen the uv_build ceiling to <0.13.
  • Bump the scaffold Dockerfile's uv image to 0.12.1 so newly generated workers don't reintroduce the mismatch, with tests/test_init.py following the tag.

The downstream effect only lands once a release tag carries the new ceiling; existing worker repos keep their own committed 0.11.25 Dockerfile pin.

Verified with uv sync --locked --all-groups (rebuilds clean, no warning) and uv run pytest.

Outside the declared uv_build range, uv falls back to an isolated PEP 517
build that downloads the backend from PyPI. Scaffolded workers install this
package from a source tarball, so the fallback hit every worker image build.
@vinismarques
vinismarques merged commit 44a1620 into main Aug 5, 2026
1 check passed
@vinismarques
vinismarques deleted the chore/uv-0.12 branch August 5, 2026 00:10
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