Repository navigation
build: uv.lock hygiene (normalise markers, require uv 0.8+, --locked everywhere) - #157
Open
renato-umeton wants to merge 6 commits into
Open
renato-umeton wants to merge 6 commits into
renato-umeton wants to merge 6 commits into
Conversation
uv 0.12 drops redundant python_full_version markers in 13 entries the first time it re-resolves the lock (23 removed, 1 simplified on tzdata). Relocking with uv 0.12.19 records that form once, so CI and contributors on a current uv stop producing a marker only diff. No package, version or source changes; uv 0.8.22 and 0.11.10 accept the result with uv lock --check.
uv 0.7 rewrites uv.lock to revision 2, which already slipped into a PR once. required-version under [tool.uv] makes an older uv stop with an error before it touches the lock. The lock itself is unchanged.
The test job already fails on a stale uv.lock; the docs and pre-commit jobs quietly relocked instead. A test now checks that every uv sync in the workflows passes --locked.
Nothing documented the uv version floor, how to change dependencies, or how to settle a uv.lock conflict, and hand edits have caused trouble before. Add a short section to DEVELOPMENT.md.
The pip ecosystem bumps pyproject.toml without touching uv.lock, so its PRs would fail every job that now syncs with --locked. The uv ecosystem updates both files. Directory and schedule are unchanged.
Contributor
Coverage report
This PR does not seem to contain any modification to coverable code. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
follow up to #147, a few small lock things
uv lock --checkon it, and 0.12.20 (what CI gets today) leaves it byte identical[tool.uv] required-version = ">=0.8"so uv 0.7 stops w/ an error before it rewrites the lock to revision 2 (bit us once in fix: refuse unknown RAI config keys and correct the social impact key in the template #134)uv sync --lockedlike test.yaml, + a test that parses the workflows and checks everyuv synchas--lockeduv lock,git add, no hand edits)heads up: if u are on uv 0.7 (i was, 0.7.22)
uv runwill now refuse, plsuv self updateorbrew upgrade uvmerge-tree vs the open lock PRs:
uv lock --checkand the lock tests pass on the ci: publish test coverage as a README badge and pull request comment #135 merge (its test.yaml has a comment mentioning uv sync, the test ignores comments)uv lockw/ 0.12.19) gives feat: add a local MCP server and an Agent Skill #130's lock byte for bytesuggested merge order: #148, this one, #141, #135, #130 last (resolve w/ the recipe in DEVELOPMENT.md)
thx!