Bump mypy from 2.1.0 to 2.2.0

[dependabot]

Bumps mypy from 2.1.0 to 2.2.0.

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next Release

Packaging changes

• No longer provide mypyc-accelerated wheels for macOS x86_64 [mypyc-wheels #119](mypyc/mypy_mypyc-wheels#119)

Mypy 2.3

We've just uploaded mypy 2.3.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.

The Upcoming Switch to the New Native Parser

We are planning to enable the new native parser (--native-parser) by default soon. We recommend that you test the native parser in your projects and report any issues in the mypy issue tracker.

Mypyc Free-threading Memory Safety

Free-threaded Python builds that don't have the GIL require additional synchronization primitives or lock-free algorithms to ensure memory safety when there are race conditions (for example, when a thread reads a list item while another thread writes the same list item concurrently). This release greatly improves memory safety of free threading.

List operations are now memory-safe on free threaded Python builds, even in the presence of race conditions. This has some performance cost. For list-heavy workloads, using librt.vecs.vec instead of list is often significantly faster, but note that vec is not (and likely won't be) fully memory safe, and the user is expected to avoid race conditions. The newly introduced librt.threading.Lock helps with this. Using variable-length tuples can also be more efficient than lists, since tuples are immutable and don't require expensive synchronization to ensure memory safety.

Instance attribute access is also (mostly) memory safe now on free-threaded builds in the presence of race conditions. We are planning to fix the remaining unsafe cases in a future release.

Full list of changes:

• Make attribute access memory safe on free-threaded builds (Jukka Lehtosalo, PR 21705)
• Fix unsafe borrowing of instance attributes with free-threading (Jukka Lehtosalo, PR 21688)
• Make list get/set item more memory safe on free-threaded builds (Jukka Lehtosalo, PR 21683)
• Don't borrow list items on free-threaded builds (Jukka Lehtosalo, PR 21679)
• Make multiple assignment from list memory-safe on free-threaded builds (Jukka Lehtosalo, PR 21684)

... (truncated)

Commits

• b3c4a5b Mark release
• 396f508 [Chore] Update changelog for 2.2 (#21691)
• 9592a9e Upload wasm wheels to PyPI (#21671)
• 1dc6962 Bump ast-serialize to 0.6.0 (#21664)
• 96a7913 Bump librt to 0.12.0 (#21663)
• 5ef0902 Fix the exportjson tool (.ff cache to .json conversion) (#21628)
• 8d621ad Support --shadow-file with --native-parser (#21623)
• 74ecdd8 Sync typeshed (#21612)
• 0cd1541 [mypyc] Make function wrappers thread-safe on free-threaded builds (#21620)
• 22a9cfd [mypyc] Make list remove and index thread-safe on free-threaded builds (#21614)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

🤖 Claude Code Review

PR Code Review

Change: Bumps mypy dev/lint dependency pin from 2.1.0 to 2.2.0 in pyproject.toml (line 77). This appears to be an automated Dependabot version bump, consistent with the other recent commits in the repo history (Bump virtualenv..., Bump coverage..., Bump actions/setup-python...).

Code Quality

• ✅ Style conventions — Single-line version pin change, consistent with existing formatting in the lint dependency array (pyproject.toml:77).
• ✅ No commented-out code
• ✅ Meaningful variable names — N/A, no code logic changed.
• ✅ DRY principle — N/A.
• ✅ Defects — No logic changes; this is a pure dependency version bump. No bugs, race conditions, or memory leaks introduced. One note: mypy is a dev tool, so a version bump carries low runtime risk, but a mypy minor version bump can introduce new strict-mode checks that cause previously-passing make mypy runs to start failing. I cannot run make mypy in this environment (no network/Senzing library access), so I can't confirm CI will pass — recommend verifying make mypy succeeds locally/in CI before merge.
• ✅ .claude/CLAUDE.md review — Present in the repo, and it reads as generic project guidance (commands, architecture, structure) with no hardcoded local paths, usernames, or machine-specific settings. Nothing in this PR touches that file, and no changes are needed to it.

Testing

• ✅ N/A — no new functions, endpoints, or logic added. Existing CI/lint pipeline (make lint) is the effective test for this change.
• ⚠️ Edge cases — Since this is a tooling version bump, the real "test" is whether the upgraded mypy still passes cleanly against the existing codebase. Not verifiable from the diff alone; recommend confirming CI is green.

Documentation

• ✅ Readme — not applicable for a dependency bump.
• ✅ API docs — not applicable.
• ✅ Inline comments — not applicable, no complex logic.
• ❌ CHANGELOG.md not updated — If this repo maintains a CHANGELOG.md for dependency bumps (check repo convention), this bump isn't reflected there. Given the other recent commits (Bump virtualenv..., Bump coverage...) don't appear to have accompanying CHANGELOG entries either based on the commit log shown, this is likely consistent with existing project convention for dependabot-style bumps and probably not a blocker — but worth confirming against the repo's actual changelog policy.
• N/A Markdown/CommonMark — no .md files changed in this diff.

Security

• ✅ No hardcoded credentials
• ✅ Input validation — N/A
• ✅ Error handling — N/A
• ✅ No sensitive data in logs
• ✅ No .lic files or AQAAAD-prefixed license strings present in this diff.

Summary

This is a minimal, low-risk dependency version bump (mypy 2.1.0 → 2.2.0) with no functional code changes. It's safe to merge pending confirmation that make mypy / CI passes cleanly with the newer mypy version, since minor mypy releases occasionally add stricter checks that surface new type errors in unrelated code.

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