Repository navigation
chore(deps): bump zstd to 0.14.3 - #922
Merged
Merged
Conversation
RustSec advisories published on 2026-10-16 match zstd 0.13.3 and zstd-safe 7.2.4, including RUSTSEC-2026-0391, RUSTSEC-2026-0398, and RUSTSEC-2026-0403. zstd 0.14.3 and zstd-safe 8.2.0 fix all of them. zstd-safe 7.x gets no fix. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
fspy benchmarklinuxmacoswindows |
fengmk2
added a commit
to voidzero-dev/vite-plus
that referenced
this pull request
Nov 3, 2026
Update `zstd` from 0.13.3 to 0.13.4 and `zstd-safe` from 7.3.0 to 7.4.0 to fix [RUSTSEC-2026-0391](https://rustsec.org/advisories/RUSTSEC-2026-0391), [RUSTSEC-2026-0398](https://rustsec.org/advisories/RUSTSEC-2026-0398), and [RUSTSEC-2026-0403](https://rustsec.org/advisories/RUSTSEC-2026-0403). These releases, published on 2026-11-01, also fix the ten `zstd-safe` soundness advisories (RUSTSEC-2026-0395 through RUSTSEC-2026-0406) published alongside them. `vt` requires `zstd` `^0.13`, so this needs no vite-task bump. Only the `zstd` and `zstd-safe` entries in `Cargo.lock` change. [voidzero-dev/vite-task#922](voidzero-dev/vite-task#922) moves vite-task itself to `zstd` 0.14, and vite-plus will pick that up with the next vite-task bump. With the Security Analysis `deny.toml`, cargo-deny still reports [RUSTSEC-2026-0387](https://rustsec.org/advisories/RUSTSEC-2026-0387) in `crypto-bigint` 0.5.5, which `main` already has. The next PR in this stack fixes it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: MK (fengmk2) <fengmk2@gmail.com>
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.
Motivation
cargo denyin Vite+'s Security Analysis fails on every PR that changesCargo.lock, becausevtlockszstd0.13.3 andzstd-safe7.2.4. The check reports three vulnerabilities in these crates:zstd0.14.3.Seekable::decompresssets aVeclength beyond its capacity. Fixed inzstd-safe8.2.0.zstd-safe8.2.0.RustSec published ten more
zstd-safesoundness advisories on the same day, and 8.2.0 fixes them too. Nozstd-safe7.x release gets these fixes, so this raises the workspace requirement tozstd0.14. The lockfile changes onlyzstd,zstd-safe, andzstd-sys, and the cache archive code compiles unchanged.This repository's Security Analysis runs
cargo denyonly when a PR changesCargo.lock, so earlier PRs here did not report these advisories. On this PR it reportsadvisories ok.🤖 Generated with Claude Code