Repository navigation
Release 2.3 planning #21717
Description
This is the release tracking issue for 2.3, which I'm hoping to release on Monday Jul 13 on an accelerated schedule so that we'll have some recent mypyc features published before EuroPython (also I'll be on vacation after EuroPython for ~2.5 weeks). If any major regressions or unforeseen issues come up, we'll postpone the release date.
If there are any PRs you would like to ensure are included, please link them here.
Activity
JukkaL commentedon Jul 10, 2026
Release branch created: https://github.com/python/mypy/tree/release-2.3
I'm going to cherry-pick mypyc improvements to the release branch.
JukkaL commentedon Jul 10, 2026
Actually all the more recent non-mypyc master commitsare low-risk, so rebased the release branch on top of current master.
JukkaL commentedon Jul 10, 2026
Cherry-pick:
ilevkivskyi commentedon Jul 10, 2026
@JukkaL Should we then close #21618 and instead include 2.2 regression fixes here instead of 2.2.1? (There is already one 2.2 regression fix in master)
ilevkivskyi commentedon Jul 10, 2026
(also cc @hauntsaninja just in case)
JukkaL commentedon Jul 13, 2026
@ilevkivskyi Makes sense, I'll include any 2.2 regression fixes that are available in the 2.3 release.
JukkaL commentedon Jul 13, 2026
I'll close the 2.2 issue if/when 2.3 goes out on schedule. If 2.3 gets delayed, we can still make a 2.2.1 release.
cdce8p commentedon Jul 13, 2026
After looking at the numbers last week, I think it would make sense to stop building wheels for macOS x86_64. There are more downloads for 3.15, which is only in beta.
Update changelog for 2.3 release (#21728)
Update changelog for 2.3 release (#21728)
JukkaL commentedon Jul 13, 2026
Mypy 2.3 is released: https://mypy-lang.blogspot.com/2026/07/mypy-23-released.html
DanielNoord commentedon Aug 9, 2026
Not sure if this is the right place to ask, but do we have a tracking issue for releasing 2.4 yet? I can't seem to find it but don't want to open it prematurely.
hauntsaninja commentedon Aug 10, 2026
I don't think we do. Note if you have some sort of timeline for seeing your mypyc bug fixes released, I could also potentially do a 2.3.1
DanielNoord commentedon Aug 10, 2026
@hauntsaninja I don't want to pressure you 😄
Full context is that
isortis preparing a pretty big release that includes Python 3.15 and lazy import support. On the side I have been working on gettingmypycto work, which I just did in PyCQA/isort#2586. It would be cool to release that in the next major release as well but I have no clue how much effort it is to do a patch release. If it is a lot of work, don't bother, you probably have enough on your plate 😁hauntsaninja commentedon Aug 10, 2026
It's not a lot of effort. Please remind me if I haven't gotten it done by this weekend.
Do you need anything other than #21785 and #21826 ?
DanielNoord commentedon Aug 10, 2026
That’s appreciated!
Don’t think I need anything else. I’m building against the latest commit on
maincurrently but if you have a branch cut it’s trivial to swap out the commit hash in the PR and quickly validate the build also works with just the cherry picks!hauntsaninja commentedon Aug 15, 2026
Alright, 2.3.1 is released!
DanielNoord commentedon Aug 16, 2026
Amazing, thanks! Seems to work in our builds :)