Bump mypy from 1.20.2 to 2.0.0

[dependabot]

Bumps mypy from 1.20.2 to 2.0.0.

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next Release

Mypy 2.1

We’ve just uploaded mypy 2.1.0 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

librt.vecs: Fast Growable Array Type for Mypyc

The new librt.vecs module provides an efficient growable array type vec that is optimized for mypyc use. It provides fast, packed arrays with integer and floating point value types, which can be several times faster than list, and tens of times faster than array.array in code compiled using mypyc. It also supports nested vec objects and non-value-type items, such as vec[vec[str]].

Refer to the documentation for the details.

Contributed by Jukka Lehtosalo.

librt.random: Fast Pseudo-Random Number Generation

The new librt.random module provides fast pseudo-random number generation that is optimized for code compiled using mypyc. It can be 3x to 10x faster than the stdlib random module in compiled code.

Refer to the documentation for the details.

Contributed by Jukka Lehtosalo (PR 21433).

Mypyc Improvements

• Make compilation order with multiple files consistent (Piotr Sawicki, PR 21419)
• Fix crash on accessing StopAsyncIteration (Piotr Sawicki, PR 21406)
• Fix incremental compilation with separate flag (Vaggelis Danias, PR 21299)

Fixes to Crashes

• Fix crash on partial type with --allow-redefinition and global declaration (Jukka Lehtosalo, PR 21428)
• Fix broken awaitable generator patching (Ivan Levkivskyi, PR 21435)

Changes to Messages

... (truncated)

Commits

• 7a76500 Remove +dev from version
• 5a3ab3b Changelog for mypy 2.0 (#21422)
• f9c86e2 Some changelog updates for 2.0 (#21413)
• 519eaf1 Bump librt to 0.10.0 (#21415)
• 158a620 Fix negative narrowing for containers (#21411)
• e556eb9 Try fixing mypy mypyc wheels (#21392)
• f2c9797 Expose --num-workers and --native-parser (#21387)
• db0cb2f Bump ast-serialize cache version (#21388)
• 1090ca6 Bump ast-serialize version to 0.3.0 only (#21391)
• 714ca9f [mypyc] Add note about librt.strings thread safety (#21383)
• Additional commits viewable in compare view

[github-actions]

🤖 Claude Code Review

Code Review: mypy 1.20.2 → 2.0.0 bump

---

Code Quality

• ✅ Style guide — Single-line change in pyproject.toml, no style concerns.
• ✅ No commented-out code — N/A.
• ✅ Meaningful variable names — N/A.
• ✅ DRY principle — N/A.
• ✅ Defects — No logic errors. The version pin is straightforward. Note: mypy 2.0.0 is a major version bump and may introduce new type errors in the codebase. The CI passing (if it did) is the meaningful signal here.
• ✅ CLAUDE.md — No issues; nothing environment-specific.

Testing

• ✅ Unit/integration tests — No new code; no new tests needed.
• ✅ Coverage — N/A.

Documentation

• ❌ CHANGELOG.md — No CHANGELOG.md update is included. Dependency bumps should be logged. Check whether this project maintains a changelog and whether this bump warrants an entry (mypy 2.0.0 is a major version and could affect developer workflows).
• ✅ README / API docs — No changes needed.
• ✅ Markdown formatting — N/A.

Security

• ✅ No hardcoded credentials — N/A.
• ✅ No license files — N/A.
• ✅ No sensitive data — N/A.

---

Summary

This is a minimal, low-risk dependency bump. The only concern is whether CHANGELOG.md should be updated. Given that mypy 2.0.0 is a major version release (it dropped support for Python 3.8 and introduced breaking changes in some strict-mode checks), it's worth confirming the CI suite ran cleanly against it — particularly make mypy — before merging.

Verdict: Approve with minor note — add a CHANGELOG.md entry if the project maintains one.

Automated code review analyzing defects and coding standards

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
src/senzing_core
_helpers.py
Project Total

This report was generated by python-coverage-comment-action

[github-actions]

🤖 Claude Code Review

PR Code Review

Summary: This PR bumps mypy from 1.20.2 to 2.0.0 in pyproject.toml.

---

Code Quality

• ✅ Style guide: Single-line change in a TOML config file, no style concerns.
• ✅ No commented-out code: N/A
• ✅ Meaningful variable names: N/A
• ✅ DRY principle: N/A
• ✅ Defects: No logic errors. mypy 2.0.0 is a major version bump and may introduce breaking changes in type-checking behavior, but this is a lint dependency only — it does not affect runtime or production code. The version constraints in pyproject.toml (python_version <= '3.11' / > '3.11') are not present for mypy, suggesting it applies to all supported Python versions, which is consistent with the existing pattern for other unconstrained deps.
• ✅ CLAUDE.md: No issues; the project config is general-purpose and unaffected.

Testing

• ✅ Unit/integration tests: No application logic changed; no new tests needed.
• ⚠️ Coverage: mypy 2.0.0 is a major release and may flag new type errors not caught by 1.x. CI should be verified to confirm make mypy still passes cleanly after this bump.

Documentation

• ✅ README: No update needed.
• ✅ API docs: No update needed.
• ✅ Inline comments: N/A
• ✅ CHANGELOG.md: A dependency-only bump — no user-facing behavior change, so omitting a changelog entry is acceptable.
• ✅ Markdown formatting: N/A

Security

• ✅ No hardcoded credentials: N/A
• ✅ Input validation: N/A
• ✅ Error handling: N/A
• ✅ No sensitive data in logs: N/A
• ✅ No license files (.lic): N/A

---

Overall Assessment

APPROVE with one note: The change is minimal and correct. The only risk is that mypy 2.0.0 may introduce stricter checks that cause make mypy to fail — confirm CI passes. If it does, this bump is safe to merge.

Automated code review analyzing defects and coding standards