Upgrade zlint v3.6.4 #7897
Merged
Upgrade zlint v3.6.4 #7897
Conversation
This file contains 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.
This brings in several new and useful lints. It also brings in one CABF BR lint which we have to ignore in our default profile which includes the Subject Key Identifier extension: "w_ext_subject_key_identifier_not_recommended_subscriber". In our modern profile which omits several fields, we have to ignore the opposite RFC5280 lint "w_ext_subject_key_identifier_missing_sub_cert".
Release notes: https://github.com/zmap/zlint/releases/tag/v3.6.4
Changelog: zmap/zlint@v3.6.0...v3.6.4
Note that the majority of the ~400 file changes are merely copyright date changes.
The corresponding production config changes tracked in IN-10466 are complete.