Repository navigation
Bump tauri-plugin-updater to 2.14.1 so zip moves past the critical Dependabot alert - #1437
Merged
Merged
Conversation
…endabot alert tauri-plugin-updater 2.14.0 required zip ^4; 2.14.1 requires zip ^9, so the lockfile moves zip from 4.6.1 to 9.1.3, which is outside GHSA-m665-v7pm-7grj's vulnerable range (<= 9.0.4). The Cargo dependency disclosure is regenerated to match.
Deploying mouseterm with
|
| Latest commit: |
4983aa1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f7e2877e.mouseterm.pages.dev |
| Branch Preview URL: | https://daily-review-runs-4089367957.mouseterm.pages.dev |
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.
This bumps
tauri-plugin-updaterin the standalone app from 2.14.0 to 2.14.1, which moveszipfrom 4.6.1 to 9.1.3 and fixes the critical Dependabot alert onstandalone/src-tauri/Cargo.lock(#10, opened 2026-10-29, GHSA-m665-v7pm-7grj). The advisory coverszip≤ 9.0.4: a parser differential between a zip's two headers that can lead to arbitrary file overwrite on extraction.zipis a Windows-only dependency of the updater, which uses it to unpack update archives.cargo update -p zipcannot fix this alone, because 2.14.0 requireszip ^4and no patched 4.x exists. Upstream moved the updater tozip ^9in tauri-apps/plugins-workspace#3698, which shipped in 2.14.1.cargo update -p tauri-plugin-updater --precise 2.14.1changed:tauri-plugin-updater2.14.0 → 2.14.1, which also moves it frombase640.22 to 0.23, already in the lockfile;zip4.6.1 → 9.1.3, which dropsarbitraryandderive_arbitraryand addstyped-path0.13.0;windows-sysentries, which now resolve to the 0.61.2 already in the lockfile.The regenerated
website/src/data/dependencies-cargo.jsonreflects exactly those rows. Running the Cargo half ofwebsite/scripts/generate-deps.jsagainstmainfirst produced no diff, so the change comes from the bump alone.Every new release is past the 24-hour cooldown:
tauri-plugin-updater2.14.1 was published 2026-10-28T00:04Z,zip9.1.3 on 2026-10-27, andtyped-path0.13.0 on 2026-10-20. Renovate lists this bump in itscargogroup under "Awaiting Schedule", so without this PR it would open on Monday 2026-11-02. Its vulnerability-alert path does not act on a transitive crate here (see #1415 and #1073).The
Standalone Platform Check (windows-latest)job compiles and tests the crate againstzip9 on Windows. No CI job downloads and installs an update, so the extraction path itself is exercised only by a real release.