Repository navigation
chore: update rustix and clipboard-win dep - #27420
Open
Phoenix500526 wants to merge 1 commit into
Open
Phoenix500526 wants to merge 1 commit into
Phoenix500526 wants to merge 1 commit into
Conversation
Phoenix500526
changed the title
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.
Which issue does this PR close?
Closes #27451.
Rationale for this change
cargo auditreports an unsoundrustix 1.1.4release (RUSTSEC-2026-0486) and a yankedclipboard-win 5.4.1release.The
rustixissue can mark unwritten memory as initialized when extended-attribute functions receive a zero-length buffer. Updating to 1.1.6 fixes it. Updatingclipboard-winto 5.4.3 selects a non-yanked release.These are allowed warnings under the current audit configuration, rather than CI failures.
What changes are included in this PR?
rustixclipboard-winOnly the two package versions and checksums in
Cargo.lockchange. Existing dependency relationships andCargo.tomlconstraints are preserved.What is the testing strategy for this PR?
The existing security audit CI job covers the dependency findings. Running
bash ci/scripts/security_audit.shon the rebased local branch passes: neither therustixnor theclipboard-winwarning remains. The two unrelated unmaintained warnings are unchanged.No new tests are added because this is a lockfile-only dependency update. The full local lint and extended test suites have not been completed for the rebased branch.
Are there any user-facing changes?
Fixes the
rustixmemory-safety issue and replaces a yanked Windows clipboard dependency. No DataFusion API or configuration changes.