Update Rust crate base64 to 0.22.0

renovate[bot] commented 4 months ago

This PR contains the following updates:

Package	Type	Update	Change
base64	dependencies	minor	`0.21.7` -> `0.22.0`

Release Notes

marshallpierce/rust-base64 (base64)

### [`v0.22.0`](https://togithub.com/marshallpierce/rust-base64/blob/HEAD/RELEASE-NOTES.md#0220) [Compare Source](https://togithub.com/marshallpierce/rust-base64/compare/v0.21.7...v0.22.0) - `DecodeSliceError::OutputSliceTooSmall` is now conservative rather than precise. That is, the error will only occur if the decoded output *cannot* fit, meaning that `Engine::decode_slice` can now be used with exactly-sized output slices. As part of this, `Engine::internal_decode` now returns `DecodeSliceError` instead of `DecodeError`, 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 either `InvalidLength` or `InvalidByte` being appropriate. - Decoding is somewhat faster (5-10%)

Configuration

📅 Schedule: Branch creation - " 0-4 * 3" (UTC), 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.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 4 months ago

⚠ Artifact update problem

Renovate failed to update an artifact 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:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package base64@0.21.7 --precise 0.22.0
    Updating crates.io index
error: failed to select a version for the requirement `base64 = "^0.21.0"`
candidate versions found which didn't match: 0.22.0
location searched: crates.io index
required by package `metrics-exporter-prometheus v0.13.0`
    ... which satisfies dependency `metrics-exporter-prometheus = "^0.13.0"` (locked to 0.13.0) of package `axum-prometheus v0.6.1`
    ... which satisfies dependency `axum-prometheus = "^0.6.1"` (locked to 0.6.1) of package `star-randsrv v0.2.0 (/tmp/renovate/repos/github/brave/star-randsrv)`
perhaps a crate was updated and forgotten to be re-vendored?

rillian commented 4 months ago

I think it's confused about how to handle the Cargo.lock update between the direct dep and the indirect deps through prometheus and ppoprf. Can fix it manually, but it's not urgent, so may wait for the prometheus crate to update.

rillian commented 3 months ago

Defer this for now.

renovate[bot] commented 3 months ago

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (0.22.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

brave / star-randsrv