Skip to content

chore(deps): update rust crate base64 to 0.23 - #38

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/base64-0.x
Open

chore(deps): update rust crate base64 to 0.23#38
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/base64-0.x

Conversation

@renovate

@renovate renovate Bot commented Jul 25, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
base64 dependencies minor 0.220.23

Release Notes

marshallpierce/rust-base64 (base64)

v0.23.1

Compare Source

  • Make the tests build again on non-SIMD architectures

v0.23.0

Compare Source

  • Added more consts for preconfigured configs and engines
  • Make DecodeError::InvalidLastSymbol more clear by including the decoded value
  • Added SIMD-accelerated engines behind the default-on simd-unsafe feature: Simd picks the best
    instruction set at runtime (AVX2 on x86_64, NEON on aarch64) and falls back to the scalar
    GeneralPurpose engine, while Avx2 and Neon target one instruction set with no runtime
    detection and work in no_std. The engines support the standard and URL-safe alphabets.
  • Update MSRV to 1.71.0
  • Add support for custom padding symbols

Configuration

📅 Schedule: (UTC)

  • 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 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.

@changeset-bot

changeset-bot Bot commented Jul 25, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0f22a5c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate
renovate Bot force-pushed the renovate/base64-0.x branch from 0f22a5c to 2f349ac Compare August 6, 2026 03:22
@greptile-apps

greptile-apps Bot commented Aug 6, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

Open in Devin Review

Comment thread sdk/rust/Cargo.toml
ureq = "2"
serde_json = "1"
base64 = "0.22" # 0.5.1 — wallet_hook(privy) needs Basic auth encoding
base64 = "0.23" # 0.5.1 — wallet_hook(privy) needs Basic auth encoding

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 Verify base64 0.23 exists and API compatibility

This bumps the base64 dependency from 0.22 to 0.23. Because pre-1.0 crates treat the minor version as the semver-breaking component, 0.23 is a breaking upgrade and must actually exist on crates.io for the build to resolve. The SDK uses the engine API in sdk/rust/src/lib.rs:30 (base64::engine::general_purpose::URL_SAFE_NO_PAD.encode) and sdk/rust/src/lib.rs:234 (STANDARD.encode); if 0.23 renames or reorganizes general_purpose/Engine, both call sites need updating. There is no Cargo.lock committed for sdk/rust, so nothing here pins/validates resolution — a CI build of the SDK crate is the only signal. Worth confirming the release exists and that cargo build for sdk/rust passes before merge.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@macroscopeapp

macroscopeapp Bot commented Aug 6, 2026

Copy link
Copy Markdown

Approvability

Verdict: Needs human review

Unable to check for correctness in 2f349ac. Dependency update to base64 0.23 touches a file owned by wave-av/streaming-team (not owned by renovate bot). An open review comment raises valid concerns about verifying the new version exists and passes CI build. The designated code owners should verify this update.

No code changes detected at 7492384. Prior analysis still applies.

You can customize Macroscope's approvability policy. Learn more.

@renovate
renovate Bot force-pushed the renovate/base64-0.x branch from 2f349ac to a649734 Compare August 7, 2026 00:02
@renovate
renovate Bot force-pushed the renovate/base64-0.x branch from a649734 to 7492384 Compare August 7, 2026 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants