Repository navigation
fix(deps): Bump tauri-plugin-updater to 2.14.1 for zip 9 - #1995
Merged
Merged
Conversation
2.14.0 pinned zip ^4 (4.6.1), which carries three advisories fixed in zip 9.0.5. 2.14.1 moves to zip 9, so the lock holds one zip (9.1.0). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With zip 4.6.1 gone, the ignores would only hide these advisories if an old zip came back. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
omesser
commented
Oct 31, 2026
omesser
left a comment
Owner
Author
There was a problem hiding this comment.
Soft CLEARED
Tip: af887529
What changed
- Updater bump:
Cargo.lockmovestauri-plugin-updaterto 2.14.1, sozip9.1.0 is the onlyzipleft. - Audit ignores gone:
.cargo/audit.tomlis deleted, and thesecurity.ymlcomment no longer names it. - PR body: now lists the
windows-sysmove and the removed audit file.
What is wrong
- Nothing blocking.
Soft-FIX
- None.
Verified on the box: cargo audit passes at this tip with no ignores and only allowed warnings, nothing in the tree still names audit.toml or the three zip advisories, and the branch merges cleanly with main.
— Cursor agent (Architect), on @omesser's behalf.
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.
Summary
tauri-plugin-updater2.14.0 requiredzip ^4and locked 4.6.1, which has three advisories fixed only in zip >= 9.0.5. Upstream released 2.14.1 on 2026-10-28 withzip9 (#3698).tauri-plugin-updater = "2"already accepts 2.14.1, soCargo.tomlis unchanged. With the oldzipgone, thecargo auditignores for its advisories go too.Evidence
cargo tree -i zip --target allBefore:
After (
Cargo.lockhas onename = "zip"entry):cargo clippy --workspace --all-targets -- -D warnings: clean (macOS).cargo test --workspace: 1780 passed, 0 failed, 6 ignored.Changelog for 2.14.1: base64 0.23, and zip 9. On Windows,
Error::Extractnow wraps zip 9'sZipError. We never match that variant, so no call site changes. The updater only useszipon Windows, to unpack.zip-wrapped installers. Our release ships NSIS, andcreateUpdaterArtifactsstaysfalseuntil #200. Signatures, endpoints, and installer handling did not change.Why
windows-sysmoved. No crate changed version. Crates such aserrnoandtempfileaccept a range (>=0.52, <0.62), and the lock already held 0.60.2 forkeyring. Whencargo update -p tauri-plugin-updaterre-resolves, Cargo reuses the version already in the lock for those ranges. Running the same command on main's lockfile gives this exact file. Pinning those crates back to 0.61.2 withcargo update -p <crate> --precisedoesn't settle: each round moves a different set between 0.52, 0.59, 0.60 and 0.61. 0.60.2 is inside every affected crate's declared range, and it only matters on Windows builds.Merge Danger
Closes #1994
🤖 Generated with Claude Code
— Claude Code agent, on @omesser's behalf.