Update mypy to 2.3.0

[cdce8p]

Proposed change

Minor bugfix release.
https://mypy-lang.blogspot.com/2026/07/mypy-23-released.html

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to developer documentation pull request:
• Link to frontend pull request:

Checklist

• I understand the code I am submitting and can explain how it works.
• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• Tests have been added to verify that the new code works.
• Any generated code has been carefully reviewed for correctness and compliance with project standards.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies a diff between library versions and ideally a link to the changelog/release notes is added to the PR description.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[github-actions]

Check requirements

Checked at commit 3754f1f.

⚠️ Some checks require attention — see the details below.

Package	Old	New	No Advisories	Not Yanked	Repo Public	CI Upload	Release Pipeline	Security	PR Link	Async Safe
librt	0.12.0	0.13.0	✅	✅	✅	✅	✅	☑️	❌	✅
mypy	2.2.0	2.3.0	✅	✅	✅	⚠️	⚠️	☑️	❌	✅

📦 librt: 0.12.0 → 0.13.0

• No Advisories: ✅ No active advisories reported by PyPI for version 0.13.0.
• Not Yanked: ✅ Version 0.13.0 is a live (non-yanked) release.
• Repo Public: ✅ https://github.com/mypyc/librt is publicly accessible.
• CI Upload: ✅ Trusted Publisher attestation found (GitHub).
• Release Pipeline: ✅ OIDC via Trusted Publisher attestation (GitHub); automated CI upload verified by PyPI.
• Security: ☑️ Baseline scan found nothing obvious in pyproject.toml, lib-rt/setup.py, librt/threading.pyi. This is not a security review — only the cheap checks were run.
• PR Link: ❌ PR description should link to a changelog or compare URL on https://github.com/mypyc/librt that mentions both 0.12.0 and 0.13.0.
• Async Safe: ✅ No new blocking calls introduced in 0.12.0 → 0.13.0.

📦 mypy: 2.2.0 → 2.3.0

• No Advisories: ✅ No active advisories reported by PyPI for version 2.3.0.
• Not Yanked: ✅ Version 2.3.0 is a live (non-yanked) release.
• Repo Public: ✅ https://github.com/python/mypy is publicly accessible.
• CI Upload: ⚠️ No PEP 740 provenance attestation present on PyPI. Upload method cannot be verified from PyPI alone.
• Release Pipeline: ⚠️ Release uses a manual upload script (misc/upload-pypi.py via twine) with a static PyPI token; no automated OIDC-based publish workflow found.
• Security: ☑️ Baseline scan found nothing obvious in pyproject.toml, mypy/init.py. This is not a security review — only the cheap checks were run.
• PR Link: ❌ PR description should link to a changelog or compare URL on https://github.com/python/mypy that mentions both 2.2.0 and 2.3.0.
• Async Safe: ✅ No new blocking calls introduced in 2.2.0 → 2.3.0.

Generated by Check requirements (AW) · 116.9 AIC · ⌖ 16.9 AIC · ⊞ 31.4K · ◷

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[frenck]

Thanks, @cdce8p 👍

../Frenck

                       

Blogging my personal ramblings at frenck.dev