-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Comments
Hello! thanks for the heads up. |
Yes. The last typeshed sync was a week ago. The source commit is: python/typeshed@ff7caa3 (merged 2024-03-16). |
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 |
@svalentin I would request that #17066 is included in 1.10.0; thanks! |
Would be great if #17068 could be included as well. |
I'd appreciate if #16604 could be reviewed and included in an upcoming release (possibly this one). |
Hi everyone! Really sorry! I got carried away with other things. I'll move to doing the release from current master, commit |
Release branch - https://github.com/python/mypy/tree/release-1.10 Version bumped on master to 1.11.0+dev in d6d9d8c |
Could be good to cherry pick #16604 :-) |
Sure, let's CP that -- Done! |
Merged #17150 with an initial draft for the changelog for release 1.10. |
Mypy 1.10 released! |
Closing this as completed. Please leave a comment if there are any issues with the release and will reopen! |
I'm planning on cutting a 1.10.1 that includes #17422 Edit: this is now released |
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.
The text was updated successfully, but these errors were encountered: