Skip to content

Bump vendored helper deps to versions that actually close the advisories - #20

Merged
Krypt0ph0ne merged 1 commit into
mainfrom
deps/close-cargo-advisories
Aug 3, 2026
Merged

Bump vendored helper deps to versions that actually close the advisories#20
Krypt0ph0ne merged 1 commit into
mainfrom
deps/close-cargo-advisories

Conversation

@Krypt0ph0ne

Copy link
Copy Markdown
Owner

Replaces Dependabot PRs #15#18.

Three of those four bump into versions that are still inside their own vulnerable range, so merging them would close the PRs while leaving the alerts open:

Dependabot PR bumps to patched at closes alert?
#15 unsafe-libyaml 0.2.11 0.2.10 yes
#16 time 0.3.26 0.3.47 no
#17 serde_with 2.3.2 3.21.0 no
#18 rustix 0.36.7 0.36.16 no

This goes to the patched versions directly. serde_with needs a major bump (2.2 to 3.21); the only API the helper uses is the DeserializeFromStr derive in src/keyboard/mod.rs, unchanged in 3.x.

None of the four is reachable in this binary. The rustix issue lives in the linux_raw backend, which Darwin never selects; unsafe-libyaml's advisory states no 64-bit target is affected; and neither RFC 2822 parsing nor KeyValueMap appears anywhere in the helper source. This is supply-chain hygiene, not a fix for a live risk.

Note on provenance: Cargo.toml and Cargo.lock now diverge from the pinned upstream commit aff33824. No Rust source file is touched. Recorded in THIRD_PARTY_NOTICES.md.

Verified locally: 43 helper tests, 116 app tests, 1 hardware test skipped, 0 failures.

After merging, close #15#18.

🤖 Generated with Claude Code

The four open Dependabot PRs do not resolve their own alerts: #16 targets
time 0.3.26 (patched 0.3.47), #17 serde_with 2.3.2 (patched 3.21.0), and
#18 rustix 0.36.7 (patched 0.36.16). Only #15 (unsafe-libyaml) reaches a
fixed version. Merging all four would leave three alerts open while
looking resolved.

Go to the patched versions directly. serde_with needs a major bump, so
its requirement moves from 2.2 to 3.21; the only API used is the
DeserializeFromStr derive in src/keyboard/mod.rs, which is unchanged in
3.x. 43 helper tests and 116 app tests pass.

None of the four is reachable in this binary — the rustix issue is in the
linux_raw backend, unsafe-libyaml's affects no 64-bit target, and neither
RFC 2822 parsing nor KeyValueMap appears in the source. This is supply-
chain hygiene, not a fix for a live risk.

Cargo.toml and Cargo.lock now differ from the pinned upstream commit; no
Rust source is touched. Recorded in THIRD_PARTY_NOTICES.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant