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.10.0 Release Tracking Issue #17064

Closed
svalentin opened this issue Mar 25, 2024 · 15 comments
Closed

1.10.0 Release Tracking Issue #17064

svalentin opened this issue Mar 25, 2024 · 15 comments
Assignees
Labels
meta Issues tracking a broad area of work

Comments

@svalentin
Copy link
Collaborator

Time for the next release of MyPy!
I will be cutting the release branch today and try to release by the end of the month.

Please comment here if there are any outstanding PRs you wish to ensure are in the release branch. I will cherry-pick them if they are not merged before I cut the branch.

@svalentin svalentin added the meta Issues tracking a broad area of work label Mar 25, 2024
@svalentin svalentin self-assigned this Mar 25, 2024
@gdippolito
Copy link

Hello! thanks for the heads up.
Would this be included in the mypy 1.10 release?
Thanks

@cdce8p
Copy link
Collaborator

cdce8p commented Mar 25, 2024

Would this be included in the mypy 1.10 release?

Yes. The last typeshed sync was a week ago. The source commit is: python/typeshed@ff7caa3 (merged 2024-03-16).
The typeshed bump for mypy: cf221bd

@mr-c
Copy link
Contributor

mr-c commented Mar 26, 2024

Cool! Feel free to @ mention me in future release planning issues, so I can do a test build in Debian prior to the release :-P Maybe that (and/or formal release candidates) can avoid some of the point releases

@mr-c
Copy link
Contributor

mr-c commented Mar 26, 2024

@svalentin I would request that #17066 is included in 1.10.0; thanks!

@cdce8p
Copy link
Collaborator

cdce8p commented Mar 27, 2024

Would be great if #17068 could be included as well.

@md384
Copy link
Contributor

md384 commented Mar 31, 2024

I'd appreciate if #16604 could be reviewed and included in an upcoming release (possibly this one).

@svalentin
Copy link
Collaborator Author

svalentin commented Apr 15, 2024

Hi everyone! Really sorry! I got carried away with other things. I'll move to doing the release from current master, commit 5161ac2e5b73dc7597536eb4444219868317e5d9 for the next release which will include all the PRs mentioned in the comments above.

@svalentin
Copy link
Collaborator Author

Release branch - https://github.com/python/mypy/tree/release-1.10

Version bumped on master to 1.11.0+dev in d6d9d8c

@hauntsaninja
Copy link
Collaborator

Could be good to cherry pick #16604 :-)

@svalentin
Copy link
Collaborator Author

svalentin commented Apr 16, 2024

Sure, let's CP that -- Done!

@svalentin
Copy link
Collaborator Author

Merged #17150 with an initial draft for the changelog for release 1.10.
Please take a look or make changes if there's anything you like to point out in the blog post for the next release!

@tmke8
Copy link
Contributor

tmke8 commented Apr 24, 2024

I think #16926 is in the wrong section in the changelog. It's under "mypyc improvements" but I don't think it has anything to do with that. It might also be worthwhile to specifically highlight #16926 as a first step towards implementing PEP 695.

@svalentin
Copy link
Collaborator Author

Mypy 1.10 released!
https://mypy-lang.blogspot.com/2024/04/mypy-110-released.html

@svalentin
Copy link
Collaborator Author

Closing this as completed. Please leave a comment if there are any issues with the release and will reopen!

@hauntsaninja
Copy link
Collaborator

hauntsaninja commented Jun 23, 2024

I'm planning on cutting a 1.10.1 that includes #17422

Edit: this is now released

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

7 participants