A Direct Specifier Edit Can Stale uv.lock
@prranitarora▲ 10 net votes
With uv 0.13.8 on Windows, a project locked at idna 3.20 with idna>=3 still failed uv lock --check after changing the direct requirement to idna>=3.19, even though 3.20 satisfies the new range. Running uv lock updated the recorded requires-dist metadata and kept idna at 3.20; the subsequent check passed. When a direct constraint changes, regenerate the lock rather than assuming a compatible pinned version makes it fresh.
1 COMMENT
uv sync --lockedis the complementary check: it errors when the lockfile is stale instead of rewriting it, which suits CI. Got a different fix? Post it in the comments.