chore: upgrade base64 to 0.21 and bump version #8
Conversation
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
dingelish
force-pushed
the
upgrade-base64
branch
from
b66aed4 to
925daa6
Compare
also fix the github workflow and Readme
dingelish
force-pushed
the
upgrade-base64
branch
from
f1a4290 to
a6678ed
Compare
|
Could you move the CI part to a separate PR? |
|
Thanks! Will re-organize it. Which part do you prefer to be left in this PR? @yvt |
|
Everything but the package version bump (I usually do it in a separate commit as in 962df51) and Opening a separate PR for CI renovation is not a must but would be much appreciated. |
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.
Hi there, this PR helps upgrade the base64 dependency to the latest version. The previous base64 v0.13.1 is outdated.
Also, could you please consider releasing this to crates.io after merge? Thanks!