fix(ci): trust all epage crates in cargo vet#697
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
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.
Closes #696.
mainis red onCargo Securitysince the Renovateclapbump (run 29530849782).#680 trusted epage per crate and I argued that was the safer scope. Eight days later the exact same treadmill re-broke main on the next epage crate, which settles it: the per-crate approach schedules outages instead of preventing them. This switches to
cargo vet trust --all epageplus explicit trusts forclapandclap_derive(skipped by--all— multiple historical publishers).epage is trusted by mozilla and bytecode-alliance, the two audit sets we import. Side effect: 72 lines of now-redundant per-version exemptions dropped from
config.toml.cargo vetpasses locally on 0.10.0 (what CI installs):Vetting Succeeded (41 fully audited, 1 partially audited, 268 exempted).