-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix(deps): update rust crate base64 to 0.22 #491
Merged
Merged
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
⚠ Artifact update problemRenovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: Cargo.lock
File name: Cargo.lock
File name: Cargo.lock
File name: Cargo.lock
|
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
6 times, most recently
from
March 7, 2024 19:24
1415a4e
to
12844ce
Compare
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
5 times, most recently
from
March 16, 2024 19:18
aa32d71
to
96de00e
Compare
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
12 times, most recently
from
March 29, 2024 23:05
0675b26
to
fecb116
Compare
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
4 times, most recently
from
April 7, 2024 15:46
2866f2d
to
2ae6182
Compare
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
2 times, most recently
from
April 13, 2024 07:49
f80c9b5
to
e68abf9
Compare
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
6 times, most recently
from
July 17, 2024 21:51
8d29c5b
to
1fc41d1
Compare
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
6 times, most recently
from
July 22, 2024 17:16
32ee987
to
cbf5029
Compare
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
2 times, most recently
from
July 26, 2024 13:12
1a7dd11
to
c50bf17
Compare
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
10 times, most recently
from
August 5, 2024 09:21
3e3878a
to
700fdea
Compare
maxjoehnk
approved these changes
Aug 5, 2024
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
from
August 5, 2024 09:30
700fdea
to
ad75908
Compare
renovate
bot
force-pushed
the
renovate/base64-0.x
branch
from
August 5, 2024 09:41
ad75908
to
b091611
Compare
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.
This PR contains the following updates:
0.21
->0.22
Release Notes
marshallpierce/rust-base64 (base64)
v0.22.1
Compare Source
alphabet::BIN_HEX
.v0.22.0
Compare Source
DecodeSliceError::OutputSliceTooSmall
is now conservative rather than precise. That is, the error will only occur if the decoded output cannot fit, meaning thatEngine::decode_slice
can now be used with exactly-sized output slices. As part of this,Engine::internal_decode
now returnsDecodeSliceError
instead ofDecodeError
, but that is not expected to affect any external callers.DecodeError::InvalidLength
now refers specifically to the number of valid symbols being invalid (i.e.len % 4 == 1
), rather than just the number of input bytes. This avoids confusing scenarios when based on interpretation you could make a case for eitherInvalidLength
orInvalidByte
being appropriate.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.