chore(deps): bump base64 from 0.22.1 to 0.23.1 - #5875
Conversation
Bumps [base64](https://github.com/marshallpierce/rust-base64) from 0.22.1 to 0.23.1. - [Changelog](https://github.com/marshallpierce/rust-base64/blob/master/RELEASE-NOTES.md) - [Commits](marshallpierce/rust-base64@v0.22.1...v0.23.1) --- updated-dependencies: - dependency-name: base64 dependency-version: 0.23.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
Thanks @dependabot[bot] for taking the time to contribute. This repository is observing a maintainer-managed PR intake gate in dry-run mode, so this pull request is staying open. This note helps maintainers prepare the allowlist before any enforcement is considered. Please read |
|
Claude finished @Hmbown's task in 1m 3s —— View job Review: bump
|
There was a problem hiding this comment.
Codewhale review
Dependabot bumps base64 from 0.22.1 to 0.23.1 in crates/tui/Cargo.toml and updates Cargo.lock. This is a breaking 0.x semver update that raises MSRV to 1.71.0 and changes DecodeError::InvalidLastSymbol; no source or test updates are included.
Findings
- [WARNING] MSRV raised to 1.71.0 (
crates/tui/Cargo.toml:50)
base64 0.23.0 raises the minimum supported Rust version to 1.71.0. If this repository targets an earlier Rust version, CI or downstream builds will fail. Verify the workspace MSRV policy before merging. - [WARNING] Potential breaking change in DecodeError::InvalidLastSymbol (
crates/tui/Cargo.toml:50)
base64 0.23.0 changed DecodeError::InvalidLastSymbol to include the decoded value. Any exhaustive pattern match on DecodeError variants in the tui crate will need updating. The PR contains only manifest changes, so this was not verified by source edits; run cargo test -p codewhale-tui after merging/rebase. - [INFO] Default simd-unsafe feature now enabled (
crates/tui/Cargo.toml:50)
base64 0.23.0 adds SIMD-accelerated engines behind a default-onsimd-unsafefeature. If dependency policy restricts unsafe code or default features are expected to be minimal, evaluate settingdefault-features = falseand choosing an explicit engine. - [INFO] No test/CI results for breaking dependency bump (
Cargo.lock:1058)
For a 0.x dependency bump, the PR should be validated by running the crate's test suite (cargo test -p codewhale-tui) and ideallycargo check --workspace. The diff does not include any accompanying test or CI outcome.
Assessment
The dependency bump is straightforward but carries semver-breaking changes and an MSRV rise. It should only be merged after CI confirms compatibility with the workspace MSRV and source code compiles and tests successfully.
Advisory review by Codewhale (codewhale review --pr 5875 --post, head 23a7014355548ee096544a25adaeb4b57ed71eb8). Line-specific findings are also posted as inline review comments; mechanical fixes arrive as committable suggestions you can apply from the Files tab. CODEOWNERS approval still governs merge.
| async-stream = "0.3.6" | ||
| async-trait.workspace = true | ||
| base64 = "0.22.1" | ||
| base64 = "0.23.1" |
There was a problem hiding this comment.
[WARNING] MSRV raised to 1.71.0
base64 0.23.0 raises the minimum supported Rust version to 1.71.0. If this repository targets an earlier Rust version, CI or downstream builds will fail. Verify the workspace MSRV policy before merging.
| async-stream = "0.3.6" | ||
| async-trait.workspace = true | ||
| base64 = "0.22.1" | ||
| base64 = "0.23.1" |
There was a problem hiding this comment.
[WARNING] Potential breaking change in DecodeError::InvalidLastSymbol
base64 0.23.0 changed DecodeError::InvalidLastSymbol to include the decoded value. Any exhaustive pattern match on DecodeError variants in the tui crate will need updating. The PR contains only manifest changes, so this was not verified by source edits; run cargo test -p codewhale-tui after merging/rebase.
| async-stream = "0.3.6" | ||
| async-trait.workspace = true | ||
| base64 = "0.22.1" | ||
| base64 = "0.23.1" |
There was a problem hiding this comment.
[INFO] Default simd-unsafe feature now enabled
base64 0.23.0 adds SIMD-accelerated engines behind a default-on simd-unsafe feature. If dependency policy restricts unsafe code or default features are expected to be minimal, evaluate setting default-features = false and choosing an explicit engine.
| "async-trait", | ||
| "axum", | ||
| "base64 0.22.1", | ||
| "base64 0.23.1", |
There was a problem hiding this comment.
[INFO] No test/CI results for breaking dependency bump
For a 0.x dependency bump, the PR should be validated by running the crate's test suite (cargo test -p codewhale-tui) and ideally cargo check --workspace. The diff does not include any accompanying test or CI outcome.
|
Claude finished @Hmbown's task in 1m 11s —— View job Review: bump
|
There was a problem hiding this comment.
Codewhale review
Dependabot bump of base64 from 0.22.1 to 0.23.1 in crates/tui/Cargo.toml, with matching Cargo.lock dependency reference. No application code changes are included.
Findings
- [WARNING] base64 0.23 raises MSRV to 1.71.0 (
crates/tui/Cargo.toml:51)
The 0.23.0 release explicitly updates the minimum supported Rust version to 1.71.0. If this workspace supports older toolchains or has an MSRV policy below 1.71, this bump will break builds for those users/CI jobs. Confirm the workspace MSRV before merging. - [INFO] DecodeError::InvalidLastSymbol payload may have changed
Release notes state thatDecodeError::InvalidLastSymbolnow includes the decoded value. If any base64 decoding code in crates/tui matches exhaustively onDecodeErrorvariants, it may fail to compile after this bump. A quick grep forInvalidLastSymbolorDecodeErroris warranted. - [INFO] New default
simd-unsafefeature (crates/tui/Cargo.toml:51)
base64 0.23 introduces SIMD-accelerated engines behind the default-onsimd-unsafefeature. This is generally fine, but it is a new default feature with unsafe code; if the project has strict safety/audit or no_std constraints, confirm it is acceptable.
Assessment
The dependency bump is likely safe and should be mergeable after verifying MSRV compatibility and checking for exhaustive DecodeError matching. Running the existing test suite for crates/tui is important because no source changes are included.
Advisory review by Codewhale (codewhale review --pr 5875 --post, head 677b7fc924e3149e708b10078a0b8fb652ff2b92). Line-specific findings are also posted as inline review comments; mechanical fixes arrive as committable suggestions you can apply from the Files tab. CODEOWNERS approval still governs merge.
| async-trait.workspace = true | ||
| base64 = "0.22.1" | ||
| base64 = "0.23.1" | ||
| axum.workspace = true |
There was a problem hiding this comment.
[WARNING] base64 0.23 raises MSRV to 1.71.0
The 0.23.0 release explicitly updates the minimum supported Rust version to 1.71.0. If this workspace supports older toolchains or has an MSRV policy below 1.71, this bump will break builds for those users/CI jobs. Confirm the workspace MSRV before merging.
| async-trait.workspace = true | ||
| base64 = "0.22.1" | ||
| base64 = "0.23.1" | ||
| axum.workspace = true |
There was a problem hiding this comment.
[INFO] New default simd-unsafe feature
base64 0.23 introduces SIMD-accelerated engines behind the default-on simd-unsafe feature. This is generally fine, but it is a new default feature with unsafe code; if the project has strict safety/audit or no_std constraints, confirm it is acceptable.
Bumps base64 from 0.22.1 to 0.23.1.
Changelog
Sourced from base64's changelog.
Commits
069bf70v0.23.16ab1fb0Merge pull request #310 from musicinmybrain/test-on-non-simd-arches7cffce6Fix testing on architectures without unsafe SIMD supporte34f9a0Merge pull request #308 from atouchet/come9240c9Remove outdated comment9e9220av0.23.0870326eMerge pull request #306 from marshallpierce/mp/trailing-bits-docsfbec5f1Document no trailing trailing bits0a23549Merge pull request #305 from marshallpierce/mp/edition-2021f10b7e2Update deps & editionDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)