Change back from mypy-dev to mypy. There are only some minor changes between the last used version and the now released 1.10.0. All major improvements / bug fixes could already used with mypy-dev.
If there are some notable commits in the future, it might make sense to temporarily change back to mypy-dev.
Type of change
[x] 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:
Checklist
[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
Proposed change
Release notes: https://mypy-lang.blogspot.com/2024/04/mypy-110-released.html Diff compare: https://github.com/python/mypy/compare/4310586460e0af07fa8994a0b4f03cb323e352f0...v1.10.0
Change back from
mypy-dev
tomypy
. There are only some minor changes between the last used version and the now released1.10.0
. All major improvements / bug fixes could already used withmypy-dev
.If there are some notable commits in the future, it might make sense to temporarily change back to
mypy-dev
.Type of change
Additional information
Checklist
ruff format homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.To help with the load of incoming pull requests: