You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mlir_aie_wheels: regenerate lockfiles without the uv dependency
The previous commit's switch to `uv pip compile --universal` solved
the cross-platform-resolution problem (delvewheel-on-Linux drops it
from the lock), but added uv as a new tool the maintenance workflow
depends on. Backing that out:
- ci-tools.in: drop the `; platform_system == "Windows"` marker on
delvewheel. delvewheel ships as a universal `py3-none-any` wheel,
so installing it on Linux is harmless (~50 KB unused). With no
Windows-only entry left, plain pip-compile from a Linux host
resolves the file correctly. auditwheel + patchelf keep their
Linux markers (those genuinely have no Windows wheel).
- requirements.lock: regenerated with pip-compile inside a Python
3.10 container (`docker run --rm python:3.10-slim ...`). Numpy
still pins to 2.2.6 — the matrix-Python fix from the prior commit
is unchanged.
The refresh recipe in ci-tools.in is updated back to plain
pip-compile, with a one-line note explaining why delvewheel is
intentionally unmarked.
Co-Authored-By: Claude Opus 4 (1M context) <noreply@anthropic.com>
0 commit comments