Upgrade to Axum 0.6.4 #17560
Closed
Upgrade to Axum 0.6.4 #17560
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
antiguru
approved these changes
Feb 8, 2023
Now that tokio-rs/axum#1598 has been included in a release, we can resume tracking the official releases.
arusahni
force-pushed
the
chore/bump-stable-axum
branch
from
bafb3e2
to
49e6c48
Compare
|
Unfortunately axum's bump to base64 v0.20 is going to be very irritating. There's a bunch of other crates in the ecosystem that are still using base64 v0.13. |
|
Upgraded on main via another PR! |
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.
Motivation
Now that tokio-rs/axum#1598 has been included in a release, we can resume tracking the official releases.
Checklist
$T ⇔ Proto$Tmapping (possibly in a backwards-incompatible way) and therefore is tagged with aT-protolabel.