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.
cargo audit
works normally and does not require any changes., but this makes the current linter barf because of unknown fieldwithdrawn
.I have linter with validation for these fields in the
osv
branch. We could publish that as a pre-release, that would also require a pre-release ofrustsec
crate.Another approach is to extract just the linter changes (they seem to be self-contained) and publish a new release. That should work in theory, but I haven't tested that.
Only @tarcieri currently has the permissions to publish
rustsec-admin
; adding as a reviewer.