Repository navigation
build(linux): allow the yanked zip 8.6.0 rust_xlsxwriter still needs - #3440
Merged
Merged
Conversation
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
1 participant
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.
Why
The Supply chain check now fails on every Linux PR: zip yanked every 8.x release after three advisories, and
cargo denydenies yanked crates.rust_xlsxwriter0.99.1, its newest release, still requireszip ^8.3, soCargo.lockcan't move off 8.6.0.Change
deny.tomlallows the yankedzip@8.6.0with its reason. GHSA-4v9h-p7m9-rh26, GHSA-vv5m-jxxh-4627 and GHSA-4684-h2q9-2vcp are all in archive extraction.rust_xlsxwriteronly writes archives, and core's export test reads entries without extracting.rust_xlsxwritertakes zip 9.Verified
cargo deny --locked check advisories bans licenses sources0.20.2 passes.