chore(deps): bump base64 from 0.22 to 0.23 - #3849
Open
paolobarbolini wants to merge 1 commit into
Open
Conversation
paolobarbolini
force-pushed
the
base64-0.23
branch
from
July 27, 2026 10:47
598be6f to
f0683f3
Compare
Collaborator
|
Please check the error from the CI |
Collaborator
|
There also seem to be 5 other dependencies of ours through which we keep pulling the older version so you might want to send PRs their way if you didn't already. |
Contributor
Author
|
This is now waiting on hyperium/headers#233 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
base64v0.23 was released 4 days ago. The ecosystem is starting to upgrade and projects are starting to get duplicate dependency versions of base64.Solution
Upgrade axum to v0.23 so that we are 1 dependency closer to not depending on v0.22 anymore.