build(deps-dev): re-lock uv.lock against the mypy>=2.3.0 dev pins - #965
Open
justinmclean wants to merge 1 commit into
Open
build(deps-dev): re-lock uv.lock against the mypy>=2.3.0 dev pins#965justinmclean wants to merge 1 commit into
justinmclean wants to merge 1 commit into
Conversation
3 tasks
22 tasks
potiuk
pushed a commit
that referenced
this pull request
Jul 27, 2026
…11 (#968) Match requires-python, ruff, and mypy to the repo-wide 3.11 floor so type-checking cannot green-light constructs unsupported by the declared runtime. Apply the py311 ruff UP017/B905 fixes that the raised target-version now surfaces. Also re-lock root uv.lock mypy requires-dev specifiers to >=2.3.0 so prek stops rewriting the lock on every README-touching commit (same correction as #965). Generated-by: Cursor Grok 4.5 Signed-off-by: shaurya2k06 <shaurya2k06@gmail.com>
22 tasks
justinmclean
pushed a commit
that referenced
this pull request
Jul 27, 2026
…vers (#970) Correct the license-size docstring to bytes, skip the live header integration out-of-tree instead of aborting, and catch OSError from validate_eval_coverage directory listing the same way collect_tool_python_files does. Also re-lock root uv.lock mypy requires-dev specifiers to >=2.3.0 so prek stops rewriting the lock when this tool is touched (same correction as #965). Signed-off-by: shaurya2k06 <shaurya2k06@gmail.com>
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.
Summary
uv.lockso the[package.metadata.requires-dev]blocks match what the manifests already declare. Eight workspace members were bumped tomypy>=2.3.0in theirpyproject.tomlbut the lock still recorded>=2.1.0for them:checker,generate-cve-json,oauth-draft,redactor,sandbox-lint,skill-and-tool-validator,skill-evals,vulnogram-api.mypyitself is already pinned at2.3.0in the resolved set; this only corrects the recorded specifiers, which are derived frompyproject.toml.prekhooks invokeuv run --project <tool>without--frozenor--locked, so every hook run re-locks and writes this pending correction into whichever branch happens to be checked out. Contributors keep picking up eight lines of unrelateduv.lockchurn in feature PRs, which then reads as scope creep in review. Landing the correction on its own clears it for everyone.Type of change
.claude/skills/<name>/) — eval fixtures updated belowtools/<system>/*.md)tools/*/withpyproject.toml)docs/,README.md,CONTRIBUTING.md)projects/_template/)prek, workflows, validators)Test plan
prek run --all-filespassesuv run pytest/ruff check/mypypasses(
PYTHONPATH=tools/skill-evals/src python3 -m skill_evals.runner tools/skill-evals/evals/<skill>/)(a regression test for the bug fixed / the behaviour added — see CONTRIBUTING.md)