Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.11 Release Tracking Issue #17285

Closed
koogoro opened this issue May 24, 2024 · 29 comments
Closed

1.11 Release Tracking Issue #17285

koogoro opened this issue May 24, 2024 · 29 comments
Labels
meta Issues tracking a broad area of work

Comments

@koogoro
Copy link
Collaborator

koogoro commented May 24, 2024

It's time for the next public release!
I'll probably cut the branch at 43a605f.

If there's any fixes or really important changes you'd like to make the cut, please post them here.

@koogoro koogoro added the meta Issues tracking a broad area of work label May 24, 2024
@koogoro
Copy link
Collaborator Author

koogoro commented May 24, 2024

bug found: #17286
edit: not a bug! 🎉

@JelleZijlstra
Copy link
Member

JelleZijlstra commented May 25, 2024

Probably good to include #17284 and #17292

@cdce8p
Copy link
Collaborator

cdce8p commented May 25, 2024

Can we include these two PRs for PEP 695?

@tusharsadhwani
Copy link
Contributor

+1 for #17268 if possible

@DanieleIsoni
Copy link

Is it possible to add also #17357 for the experimental feature NewGenericSyntax

@ngnpope
Copy link

ngnpope commented Jun 14, 2024

Would love #17371, #17376, and #17382 if possible.

@hauntsaninja
Copy link
Collaborator

Can we cherry pick #17420 ? I'm currently cutting a 1.10.1 patch release for this, so would be good to make sure that 1.11 also includes it.

@picnixz
Copy link
Contributor

picnixz commented Jun 23, 2024

If possible, I'd like #16849 to be included!

@hauntsaninja
Copy link
Collaborator

hauntsaninja commented Jul 1, 2024

It looks like @koogoro cut the branch at d39f023

I'm cherry picking @picnixz 's #16849 since it fixes a crash and my #17425 since it also fixes a crash and some other issues in the new functools.partial support.

This should mean everything mentioned so far will be in 1.11. Should be an exciting release :-)

We may also want to cherry pick #17462 (edit: I cherry picked this as well)

@hxyannay
Copy link

Hey, is there any expectation on when 1.11 will be released?
Really waiting forward to the new features :)

@koogoro
Copy link
Collaborator Author

koogoro commented Jul 10, 2024

Hey, is there any expectation on when 1.11 will be released? Really waiting forward to the new features :)

Hopefully in the next week or two!

@svalentin
Copy link
Collaborator

Looks like we found an assertion error crash in the new version: #17515

@JukkaL
Copy link
Collaborator

JukkaL commented Jul 18, 2024

I cherry-picked a fix to the crash from master:

@ash-sony
Copy link

Just dropping a thanks to all the people who contributed to this release! Tons of really nice additions to the library.

@koogoro
Copy link
Collaborator Author

koogoro commented Jul 19, 2024

I've made the release: https://mypy-lang.blogspot.com/2024/07/mypy-111-released.html
I'll leave the issue open for a couple weeks in case there's anything like a new crash that might necessitate a point release.

@hauntsaninja
Copy link
Collaborator

If we make a point release, we should include #17543

@hauntsaninja
Copy link
Collaborator

hauntsaninja commented Jul 22, 2024

Also #17558 and #17563

@sobolevn
Copy link
Member

Should we include some kind of an easter egg for 1.11.1 release? 😊

@Avasam
Copy link
Contributor

Avasam commented Jul 25, 2024

Can point releases include typeshed sync? (I'd like my recent distutils update to use in setuptools) Or is that against policy?

@cdce8p
Copy link
Collaborator

cdce8p commented Jul 25, 2024

Can point releases include typeshed sync? (I'd like my recent distutils update to use in setuptools) Or is that against policy?

Usually those are only included with new minor releases as the frequently also create new typing issues.

@andersk
Copy link
Contributor

andersk commented Jul 26, 2024

Please include this 1.11 regression fix:

(This is different from #17495.)

@hauntsaninja
Copy link
Collaborator

I cherry picked the four commits mentioned to the 1.11 branch.
I can cut a release on Monday (I'll be afk for most of the weekend), if someone wants to before then, please do!

@hauntsaninja
Copy link
Collaborator

1.11.1 is released

@md384
Copy link
Contributor

md384 commented Aug 5, 2024

Can we get bug fix release with b56f357 please?

@mr-c
Copy link
Contributor

mr-c commented Aug 13, 2024

Will there be a mypy 1.11.2 ? the regression fixed by #17639 is holding up the mypy package in Debian. If not, I will try to backport the fix.

@hauntsaninja
Copy link
Collaborator

hauntsaninja commented Aug 14, 2024

I don't have much time for mypy right now, but if someone fixes the conflicts and makes backport PRs to the 1.11 branch that will increase your odds

@mr-c
Copy link
Contributor

mr-c commented Aug 14, 2024

@hauntsaninja 👍 #17675

@md384
Copy link
Contributor

md384 commented Aug 14, 2024

@hauntsaninja @mr-c I have created #17677 with the changes from #17675 and my request #17285 (comment)

@hauntsaninja
Copy link
Collaborator

Okay, I've cut a 1.11.2 with the above

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues tracking a broad area of work
Projects
None yet
Development

No branches or pull requests