Version 0.20.1 #1644
Merged
Version 0.20.1 #1644
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kludex
commented
May 22, 2022
|
I've moved #1377 to next milestone, as I think there are some missing things there. |
Kludex
requested review from
abersheeran,
adriangb,
florimondmanca,
tomchristie and
aminalaee
adriangb
approved these changes
May 28, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Diff: 0.20.0...master
GitHub draft release: /~https://github.com/encode/starlette/releases/tag/untagged-9a4cc4b7f495dd7500e6
Checklist:
MultiPartExceptionwhen missing "name" field onContent-Dispositionheader #1643Allow staticfiles to follow symlinks outside directory #1377Moved to the next milestone.Preserve changes to contexvars made in threadpools #1258Removed from this milestone, as the changes can be done onanyio. Under investigation. See that PR for more information.The checklist is not a blocker, we can already release 0.20.1. They are the missing PRs on the
0.20.1milestone - which I'd like to have a decision if we should merge, but it can be postponed.I guess none of those are a reason for a minor bump (?).