Fix mypy v2 plugin for upcoming mypy release

[cdce8p]

Change Summary

Similar to #12207, but for the v2 mypy plugin.
Seems my tests didn't trigger that part which is why I missed it earlier.

Some background: python/mypy#19768 (comment)

Related issue number

Checklist

• The pull request title is a good summary of the changes - it will be used in the changelog
• Unit tests for the changes exist
• Tests pass on CI
• Documentation reflects the changes where applicable
• My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @Viicos

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
pydantic
mypy.py
Project Total

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

[codspeed-hq]

CodSpeed Performance Report

Merging #12209 will not alter performance

_{Comparing cdce8p:fix-mypy-plugin (3daa7b7) with main (0054305)}

Summary

✅ 46 untouched benchmarks

[cdce8p]

please review

[Viicos]

Thanks again

[cdce8p]

Are there any plans to do a new release soon?

The next mypy version is expected to be released next week. See python/mypy#19764 (comment)
There is also the Python 3.14 support which would be awesome to have in a production release. This would allow downstream packages and applications to start adding compatibility themselves.

[Viicos]

While a bit tight, we should be able to come with a final 2.12 release beginning of October, so right before the 3.14 release. I'll kick a beta release in a couple release, so that it can at least be used with mypy in the meanwhile.

[cdce8p]

Thanks for the update!

[DanielNoord]

Is there any chance this can be backported to the 2.11 branch? mypy is reporting significant performance gains in this release and we'd like to start using that as soon as possible.

This seems like a small enough change to backport?

[Viicos]

Is there any chance this can be backported to the 2.11 branch? mypy is reporting significant performance gains in this release and we'd like to start using that as soon as possible.

This seems like a small enough change to backport?

Yeah given that mypy 1.18 got released already, I think it makes sense.

[Viicos]

Releases out:

https://pypi.org/project/pydantic/1.10.23/
https://pypi.org/project/pydantic/2.11.8/

[cdce8p]

Thanks for new releases @Viicos!

Unfortunately, v1/mypy.py is still broken though. Seems #12207 wasn't merged back into the v2.11-fixes branch beforehand.

[Viicos]

My bad, such backporting happens so rarely that it is done manually, so this was bound to happen 😅

Published 2.11.9.

[cdce8p]

No problem. Thanks again! One last thing. Would you mind approving the workflow so the version is actually pushed to PyPI?
https://github.com/pydantic/pydantic/actions/runs/17695540042

[DanielNoord]

Thanks @Viicos @cdce8p.

It is not common for packages to go out of their way to expedite patch releases for such small fixes, and I know how annoying it can be to do so.

Highly appreciated that you did so. By me, but likely by many others!