Skip to content
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

Update Rust crate base64 to 0.22.0 #960

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 10, 2024

This PR contains the following updates:

Package Type Update Change
base64 dependencies minor 0.21.5 -> 0.22.0

Release Notes

marshallpierce/rust-base64 (base64)

v0.22.1

Compare Source

  • Correct the symbols used for the predefined 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 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 - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot enabled auto-merge (squash) February 10, 2024 04:45
Copy link
Contributor Author

renovate bot commented Feb 10, 2024

⚠ Artifact update problem

Renovate 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:

  • 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 signer/Cargo.toml --workspace
    Updating crates.io index
error: failed to get `ledger-mob-apdu` as a dependency of package `ledger-mob v0.16.0 (/tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/lib)`
    ... which satisfies path dependency `ledger-mob` (locked to 0.16.0) of package `mc-full-service v2.10.1 (/tmp/renovate/repos/github/mobilecoinofficial/full-service/full-service)`

Caused by:
  failed to load source for dependency `ledger-mob-apdu`

Caused by:
  Unable to update /tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/apdu

Caused by:
  failed to parse manifest at `/tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/apdu/Cargo.toml`

Caused by:
  the cargo feature `per-package-target` requires a nightly version of Cargo, but this is the `stable` channel
  See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
  See https://doc.rust-lang.org/cargo/reference/unstable.html#per-package-target for more information about using this feature.

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path full-service/Cargo.toml --workspace
    Updating crates.io index
error: failed to get `ledger-mob-apdu` as a dependency of package `ledger-mob v0.16.0 (/tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/lib)`
    ... which satisfies path dependency `ledger-mob` (locked to 0.16.0) of package `mc-full-service v2.10.1 (/tmp/renovate/repos/github/mobilecoinofficial/full-service/full-service)`

Caused by:
  failed to load source for dependency `ledger-mob-apdu`

Caused by:
  Unable to update /tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/apdu

Caused by:
  failed to parse manifest at `/tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/apdu/Cargo.toml`

Caused by:
  the cargo feature `per-package-target` requires a nightly version of Cargo, but this is the `stable` channel
  See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
  See https://doc.rust-lang.org/cargo/reference/unstable.html#per-package-target for more information about using this feature.

@renovate renovate bot requested a review from a team February 10, 2024 04:45
@codecov-commenter
Copy link

codecov-commenter commented Feb 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.13%. Comparing base (ab2af32) to head (2d20373).
Report is 212 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #960      +/-   ##
==========================================
+ Coverage   60.12%   69.13%   +9.01%     
==========================================
  Files          88      125      +37     
  Lines       12356    16687    +4331     
  Branches     2010     2798     +788     
==========================================
+ Hits         7429    11537    +4108     
- Misses       3238     5150    +1912     
+ Partials     1689        0    -1689     
Flag Coverage Δ
69.13% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/base64-0.x branch 4 times, most recently from 79fbc8b to da41ba8 Compare February 14, 2024 22:35
@renovate renovate bot force-pushed the renovate/base64-0.x branch 2 times, most recently from f1d10da to ac452eb Compare February 23, 2024 15:32
@renovate renovate bot force-pushed the renovate/base64-0.x branch from ac452eb to 3728199 Compare March 2, 2024 04:40
@renovate renovate bot changed the title Update Rust crate base64 to 0.21.7 Update Rust crate base64 to 0.22.0 Mar 2, 2024
@renovate renovate bot force-pushed the renovate/base64-0.x branch from 3728199 to 0969abb Compare March 6, 2024 06:47
@renovate renovate bot force-pushed the renovate/base64-0.x branch 3 times, most recently from 596aa79 to e0a061f Compare March 21, 2024 20:40
@renovate renovate bot force-pushed the renovate/base64-0.x branch from e0a061f to 0eacbc4 Compare April 3, 2024 04:37
@renovate renovate bot force-pushed the renovate/base64-0.x branch from 0eacbc4 to 42f50ed Compare May 1, 2024 00:28
@renovate renovate bot changed the title Update Rust crate base64 to 0.22.0 Update Rust crate base64 to 0.22.1 May 1, 2024
@renovate renovate bot force-pushed the renovate/base64-0.x branch from 42f50ed to 359d471 Compare May 5, 2024 09:08
@renovate renovate bot changed the title Update Rust crate base64 to 0.22.1 Update Rust crate base64 to 0.22.0 May 5, 2024
Copy link
Contributor Author

renovate bot commented May 20, 2024

⚠️ Artifact update problem

Renovate 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:

  • 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 full-service/Cargo.toml --workspace
    Updating crates.io index
error: failed to get `ledger-mob-apdu` as a dependency of package `ledger-mob v0.16.0 (/tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/lib)`
    ... which satisfies path dependency `ledger-mob` (locked to 0.16.0) of package `mc-full-service v2.10.5 (/tmp/renovate/repos/github/mobilecoinofficial/full-service/full-service)`

Caused by:
  failed to load source for dependency `ledger-mob-apdu`

Caused by:
  Unable to update /tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/apdu

Caused by:
  failed to parse manifest at `/tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/apdu/Cargo.toml`

Caused by:
  the cargo feature `per-package-target` requires a nightly version of Cargo, but this is the `stable` channel
  See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
  See https://doc.rust-lang.org/cargo/reference/unstable.html#per-package-target for more information about using this feature.

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path signer/Cargo.toml --workspace
    Updating crates.io index
error: failed to get `ledger-mob-apdu` as a dependency of package `ledger-mob v0.16.0 (/tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/lib)`
    ... which satisfies path dependency `ledger-mob` (locked to 0.16.0) of package `mc-full-service v2.10.5 (/tmp/renovate/repos/github/mobilecoinofficial/full-service/full-service)`

Caused by:
  failed to load source for dependency `ledger-mob-apdu`

Caused by:
  Unable to update /tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/apdu

Caused by:
  failed to parse manifest at `/tmp/renovate/repos/github/mobilecoinofficial/full-service/ledger-mob/apdu/Cargo.toml`

Caused by:
  the cargo feature `per-package-target` requires a nightly version of Cargo, but this is the `stable` channel
  See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
  See https://doc.rust-lang.org/cargo/reference/unstable.html#per-package-target for more information about using this feature.

@renovate renovate bot force-pushed the renovate/base64-0.x branch 3 times, most recently from 44cc128 to 4754210 Compare May 20, 2024 04:34
@renovate renovate bot requested a review from jgreat as a code owner May 20, 2024 04:34
@renovate renovate bot force-pushed the renovate/base64-0.x branch from 85f8815 to 998bf0b Compare June 7, 2024 21:45
@renovate renovate bot force-pushed the renovate/base64-0.x branch from 998bf0b to 8dbec9a Compare July 19, 2024 00:35
@renovate renovate bot requested a review from lnsiegel as a code owner July 19, 2024 00:35
@renovate renovate bot force-pushed the renovate/base64-0.x branch from 8dbec9a to 05aed74 Compare July 25, 2024 21:09
@renovate renovate bot force-pushed the renovate/base64-0.x branch 2 times, most recently from 7f0b203 to 78431da Compare September 10, 2024 19:57
@renovate renovate bot force-pushed the renovate/base64-0.x branch 5 times, most recently from 61333a6 to 2d20373 Compare September 24, 2024 14:02
@renovate renovate bot force-pushed the renovate/base64-0.x branch 5 times, most recently from 46ebe59 to 48300f3 Compare November 7, 2024 00:56
@renovate renovate bot force-pushed the renovate/base64-0.x branch from 48300f3 to 3777412 Compare November 8, 2024 21:09
@renovate renovate bot force-pushed the renovate/base64-0.x branch 4 times, most recently from add4c5c to bea690d Compare November 21, 2024 20:34
@renovate renovate bot force-pushed the renovate/base64-0.x branch 7 times, most recently from 8552934 to 82667bf Compare December 5, 2024 17:13
@renovate renovate bot force-pushed the renovate/base64-0.x branch from 82667bf to 1d4005d Compare December 5, 2024 20:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant