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
Prepare v3.6 release. #362
Conversation
CHANGELOG.txt
Outdated
@@ -1,5 +1,20 @@ | |||
UNRELEASED | |||
---------- | |||
3.6.0 (UNRELEASED) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Date needed before actual release.
I think this looks reasonable - can't think of anything else I'd want to pack in. |
ab7813a
to
07cd333
Compare
Hey @andrewgodwin — thanks! I've rebased. Point 3 is ready to go. I just checked, I have PyPI perms, so I can release (likely Tuesday) unless you'd like to do the honours. (Or shout 🛑 :) 🚀 |
07cd333
to
3d09ad6
Compare
Thanks @smithdc1! 🎩 |
3d09ad6
to
e079839
Compare
OK, no-one shouted — I'm going to take that as 🟢 🙂 |
`asgiref==3.6.0` introduced a new required `trailers` key to the `asgiref.types.HTTPResponseStartEvent` type. As the django/asgiref#339 code review pointed out, this is a breaking change for type checking, but it was added in a minor release, and not mentioned in the changelog. django/asgiref#339 django/asgiref#362
Hey @andrewgodwin.
I'm looking at putting out a v3.6 that we can use for Django 4.2a1.
I looked through the other PRs. I think they're all in various stages of waiting except #337.
Do you think this is right?
Can you think of anything else you want to add?
Thanks.