1.19 Release Planning

[ilevkivskyi]

We always wanted to release more often. I would propose to already aim at 1.19 release mid or late October.

cc @JukkaL

[ilevkivskyi]

From my side I would propose to:

• Stop calling --fixed-format-cache experimental
• Expose it in argparse on interpreted mypy (since we can now)
• Announce that --fixed-format-cache will be default in 1.20

[wyattscarpenter]

If #19922 (keep more readthedocs versions around) has to be done prospectively, it would be nice to enable that setting(?) on readthedocs before the next release. If old versions can easily be made retroactivity, however, this doesn't matter.

[ilevkivskyi]

Btw it may be worth highlighting #19719 in the release blog post, it is a surprisingly popular request.

[sterliakov]

Upgrading 1.18.2 to 1.19.0 cannot be performed with pip install -U. Am I missing any workarounds? If not, #20006 should probably be ALL CAPS and bold in the release notes.

[JukkaL]

Mid to late October release sounds good. @p-sawicki is expected to be the release manager.

This release will also have librt as a new dependency. It would be good to test installation in different contexts before the release goes out.

This is a release blocker (I'm working on it but have been busy recently, so not much progress):

• TypeError with async methods and inheritance mypyc/mypyc#1141

It would be nice to have free-threaded binary wheels for 3.14 (3.14t). Currently free-threaded builds use the interpreted version of mypy.

Upgrading 1.18.2 to 1.19.0 cannot be performed with pip install -U. Am I missing any workarounds?

We haven't released 1.19.0 yet. Not being able to install a release using pip install -U is a release blocker.

[sterliakov]

We haven't released 1.19.0 yet

Yep, sorry, I was trying to say that if 1.19.0 were released from current master branch, pip install -U would silently produce a broken installation.