-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
Next release planning (4.2.4) #1651
Comments
Great! Thanks! |
Looks like there are some other test failures as well. I created a draft PR to run tests with mypy 1.5: #1652 Haven't looked at the failures in detail yet. |
I described some regressed use cases in: Should we consider that a release blocker? |
Merging #1667 would change how to pin github references for |
|
I'm sorry, I've been rather absent from django-stubs during recent weeks and I'll be away from computers the whole next week. Hopefully after that we can get this release process back on track. Unless another maintainer wants to pick this up in the meanwhile. |
When is the new release expected? Thanks |
@mertcangokgoz when it is ready :) |
Done! https://github.com/typeddjango/django-stubs/releases/tag/4.2.4 I was not able to write release notes as amazingly as @intgr does, but I've covered most of the important things there. Thanks everyone! |
Mypy 1.5.0 was released today, and introduces compatibility issues with current
django-stubs
. So I'm planning to do a release soon after the compatibility is fixed:Also this MR has been sitting too long without reviews:
Known regressions:
objects
manager, of abstract models #1653The text was updated successfully, but these errors were encountered: