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.
Description
As I've mentioned before informally, the intention of this release is to be the last before we move to 1.0, not considering eventual patch releases for
0.26.0
0.27.0
.The intention is that between
0.26.0
0.27.0
and1.0
, there will be only:The idea is that between those two versions, we don't have surprises. There's already a draft release for 1.0 here - which needs to be rebased.
Checklist
Please feel free to write below if you think something should be included here, either a PR, issue, or if we need to discuss something. The list below is not necessarily what is going to be included on the release, but to take a decision - if you are against or have bad feelings about it, feel free to comment on any of them.
MiddlewareType
as a type hint for middlewares #1987raw_path
instead ofpath
in the router to be able to differentiate requests which include %2F #1828All the help here is wanted. Reviews, concerns and feedbacks are welcome. 🙏
Plan
As we discussed some months ago, on one of the encode meetings, Starlette can be considered stable, and we shouldn't even need to wait for something to happen to release 1.0. That said, we also agreed that we were going to solve some last issues and PRs, so we wouldn't need to make major releases that soon.
The plan that I had in mind is to release
0.26.00.27.0
after we solve the checklist (again, feel free to tell if you think we are missing things there), and then wait 3 or 4 weeks to release 1.0, giving time for hotfixes.cc @encode/maintainers