Repository navigation
chore: use uv dependabot ecosystem and sync uv.lock - #4846
Merged
Merged
Conversation
The pip ecosystem edits pyproject.toml but cannot maintain uv.lock, so lock files drifted behind their constraints. Both Python projects use uv (each has a uv.lock), so use the uv ecosystem to keep the lock in sync. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Manual uv lock refresh: ty 0.0.58 -> 0.0.63 (matching the >=0.0.63 constraint) and ruff 0.15.21 -> 0.15.22, catching up drift the pip-based dependabot left in the lock. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
Python Type Checking Results (Pyright)
Excluded files with errors (4 files)These files have known type errors and are excluded from CI. Remove from
|
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
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.
Summary
Dependabot's Python updates (e.g. #4843) edit
pyproject.tomlbut leaveuv.lockuntouched, so the lock drifts behind its constraints. The cause is an ecosystem mismatch in.github/dependabot.yml: both Python projects use uv (each has auv.lock), but they were configured aspackage-ecosystem: "pip", which readspyproject.tomlbut cannot maintainuv.lock.This PR:
.github/dependabot.ymlfrompiptouv, so future updates resolve through uv and commit the matchinguv.lockchanges in the same PR.tybump and resyncs the lock, catching up the drift the pip-based config left behind:pyproject.toml:ty>=0.0.62→>=0.0.63uv.lock:ty0.0.58 → 0.0.63, andruff0.15.21 → 0.15.22 (pyproject already requiredruff>=0.15.22; the lock was stale)uv lock --checkpasses.Supersedes #4843 (that PR bumps
tybut does not sync the lock).Test plan
uv lock --check— lock is consistent withpyproject.toml