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
Ship new version of axum and axum-extra #1202
Comments
Actually, we can't just ship both as non-breaking, since people could upgrade to the new version of axum without upgrading axum-extra. We'll have to backport #1171 in a way that doesn't change the number of type parameters, or have it wait until axum 0.6. |
Any updates on this? We have to work around to make |
Not yet. I've been on vacation. ETA is sometime this week. |
Oh, sorry for disturbing your vacation. Have a nice day! |
Fixes #1202 I'll update the changelogs, with notes about why 0.5.14 was yanked, in the release PR.
This was fixed in #1233 |
We accidentally shipped #1171 in a minor version which included a breaking change in axum but didn't merge a new version of axum-extra so axum-extra broke.
I've yanked axum 0.5.14 so no one can update to it.
I'll ship a new version of axum and axum-extra (that depends on the version of axum) in a week from today.
The text was updated successfully, but these errors were encountered: