-
Notifications
You must be signed in to change notification settings - Fork 1.3k
axum 0.8.0-rc.1 #3073
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
axum 0.8.0-rc.1 #3073
Conversation
yanns
left a comment
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.
Most of users will look at the changelog from axum, and will miss the ones in axum-core.
I'd suggest to copy/paste the core change log into axum. WDYT?
|
@jplatte What do you think about copy / pasting the change log? Alternatively, we could provide a link from axum to axum-core change log. But I think that the copy / paste is easier for our users. |
|
Sorry, been pretty busy. I think I'll add a link. Either way I agree that it would be good to have those entries easier to discover. |
|
I've added a note with a link. For the GH release I'll adjust it to point to the right release page. |
|
I did the same for https://github.com/tokio-rs/axum/releases/tag/axum-v0.8.0-alpha.1 |
|
Sorry, I was (and still am) a bit busier than usual. I'll definitely get back to the percent encoding, but I think we can ship the manor version without it. |
|
I figured as much and moved the percent encoding thing to the 0.9.0 milestone. But maybe that's the wrong place too? I guess it might not even be that clear whether it's going to be breaking. Anyways, I've added two more things to the 0.8.0 milestone that should probably be done before the release, will spend some time on them over the holidays and probably release around the new year if no new blockers come up. |
Closes #3060.
@yanns @mladedav I'd love to do another call for testing with all these changes in. @mladedav do you think you're gonna spend some time on the percent-encoded routing thing (not as in code, but as in getting back to the discussion)? Or should we ship without it?