chore: sync uv.lock to the already-declared black/mypy/pylint/pytest floors - #11
Merged
Merged
Conversation
…floors pyproject.toml's dev floors (black>=26.5.1, mypy>=2.3.0, pylint>=4.0.7, pytest>=9.1.1) were already bumped past what uv.lock had actually resolved (black wasn't even locked, mypy 1.15.0, pylint 3.3.6, pytest 8.3.5) — the lock was just never regenerated after the floors were raised, so `uv sync` alone wouldn't have caught it (only `uv pip install -e ".[dev]"`, matching CI, actually re-resolves against the declared floors). Same silent-drift risk the ruff incident surfaced, just not hit yet since nothing had re-locked. Unlike ruff, no new lint/type errors surfaced at the current floor versions — format-check, lint (ruff+mypy+pylint), and test all pass clean.
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
pyproject.toml's dev floors (black>=26.5.1, mypy>=2.3.0, pylint>=4.0.7, pytest>=9.1.1) were already bumped past what uv.lock had actually resolved — black wasn't even in the lock, mypy was at 1.15.0, pylint at 3.3.6, pytest at 8.3.5. The lock was just never regenerated after the floors were raised. Same silent-drift risk the ruff incident surfaced (PENDING.md), just not hit yet since nothing had re-locked.
Verified
make format-check,make lint(ruff + mypy + pylint),make testall pass clean at the new locked versions — unlike ruff, no new issues surfaced🤖 Generated with Claude Code