fix(deps): resolve memmap2 and rkyv advisories for #815 - #938
Merged
H-Chris233 merged 4 commits intoAug 10, 2026
Conversation
H-Chris233
marked this pull request as ready for review
August 10, 2026 05:09
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
enigofrom 0.2 to 0.3 in the main app and backend test workspaceenigo 0.3.0 -> xkbcommon 0.8.0 -> memmap2 0.9.11rkyvandrkyv_derivefrom 0.8.16 to 0.8.17Both
rkyv 0.8.16andrkyv 0.8.17declare Rust 1.81, so this security update does not itself raise rkyv's MSRV. Rust 1.88 matches the highest declared MSRV in the current locked dependency graph; latest stable remains the recommended development toolchain.This is the first-phase dependency fix for #815. It intentionally does not close the issue because the GTK3/glib chain and Linux runtime smoke testing remain tracked there.
Validation
cargo tree --locked --target x86_64-unknown-linux-gnu -i memmap2for both manifestscargo audit 0.22.2for both lockfiles: zero vulnerabilities; the memmap2 and rkyv advisories are gonecargo +1.88.0 metadata --locked --no-depsfor both manifestscargo +1.88.0 check --lockedfor the main appcargo +1.88.0 test --locked --manifest-path backend-tests/Cargo.toml --no-runcargo check --lockedfor the main appcargo test --locked --lib --no-runfor the main app on Windowspaste_keys_match_configured_shortcut: passedpolish_output_honors_chinese_script_preference: passedgit diff --checkCI
The desktop matrix keeps latest stable as the default toolchain and additionally installs Rust 1.88.0. Every macOS, Windows, and Linux job now:
The CI run for commit
5db682d9is pending.Remaining validation
Linux X11 and Wayland insertion smoke tests for Ctrl+V, Ctrl+Shift+V, Shift+Insert, and clipboard fallback remain tracked in #815 and are not a merge gate for this first-phase dependency PR.
Audit notes
The main lockfile retains 18 allowed warnings, including the expected GTK3/glib chain and the pre-existing
event-listener 5.4.1 / RUSTSEC-2026-0221warning. The backend test lockfile retains the unrelated allowed warninganyhow 1.0.102 / RUSTSEC-2026-0190. No RustSec ignore was added.Relates to #815.