fix(deps): bump serde_with to 3.21.0 (Dependabot #19) - #4737
Merged
Conversation
serde_with < 3.21.0 panics when KeyValueMap serializes an empty sequence or map entry (Dependabot alert #19, Moderate). Patched in 3.21.0. The crate is transitive: tauri-utils v2.9.2 is the only consumer, reached through tauri, tauri-build, tauri-codegen, tauri-macros, tauri-plugin, tauri-runtime and tauri-runtime-wry. The bump is patch-level and sits inside the existing semver range, so no manifest change is needed. serde_with_macros moves in lockstep because serde_with pins it to an exact version. Validation on Windows: cargo metadata --locked, cargo check --locked (clean, only pre-existing dead-code warnings) and cargo test --locked (164 passed, 0 failed).
This file contains hidden or 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
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.
Dependabot alert #19 (Moderate)
Advisory:
serde_with— KeyValueMap serialization panics on empty sequence or map entries.Vulnerable range
< 3.21.0; patched in 3.21.0. Detected insrc-tauri/Cargo.lock.Change:
serde_with3.20.0 → 3.21.0 (andserde_with_macros3.20.0 → 3.21.0, which moves in lockstep becauseserde_withpins its macro crate to an exact version).What pulls
serde_withinIt is entirely transitive —
src-tauri/Cargo.tomlnever names it.cargo tree -i serde_withshows a single consumer:tauri-utilsaccepts the bump inside its existing semver range, so this is a lockfile-only patch bump with no manifest change.Diff scope
One file, 4 insertions / 4 deletions — only the two
serde_withpackage entries (version + checksum each):The update was run as
cargo update -p serde_with --precise 3.21.0rather than a barecargo update, to avoid churning the rest of the lockfile. One unrelated edge that the resolver re-picked (tempfile'sgetrandom 0.4.2→0.3.4) was reverted so the diff stays limited to the advisory;cargo metadata --lockedthen exits 0, confirming the lockfile is still self-consistent.3.20.0no longer appears anywhere insrc-tauri/Cargo.lock.Validation
Run locally on Windows 11 (native Tauri target):
cargo metadata --lockedcargo check --lockedFinished dev profile— only pre-existingdead_codewarnings, no new diagnosticscargo test --lockedLinux-only members of the Tauri stack are not exercised by a Windows checkout; CI covers those.
Dependabot alert
Resolves alert #19 —
serde_with(GHSA advisory),src-tauri/Cargo.lock. The alert closes automatically once this lands onmainand the vulnerable version is no longer resolved.