-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5.1.0 Record Format updates #303
Merged
Merged
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
…schema directories to a newly created archive directory.
…e and baseSeverity validation similar to cvss 4.0
…fied copies of the FIRST schemas
changed readme to match 5.1.0 and new directory structure
@ccoffin sorry to jump into this old merged PR Was that a solution to avoid validation errors in python tooling? see RedHatProductSecurity/cvelib#87 for a related issue+solution (load json float as decimal instead of floats). |
Перестаньте мне присылать письма и удалите мой аккаунт, я не нуждаюсь в
этой рассылке …
Ср, 3 июля 2024 г. в 16:27, Loïc Jaquemet ***@***.***>:
… @ccoffin <https://github.com/ccoffin> sorry to jump into this old merged
PR
Would you remember why you merged this CVSS v4 schema change from
multipleOf to enum scores in 84a2b1e
<84a2b1e>
?
Was that a solution to avoid validation errors in python tooling?
see RedHatProductSecurity/cvelib#87
<RedHatProductSecurity/cvelib#87> for a related
issue+solution (load json float as decimal instead of floats).
—
Reply to this email directly, view it on GitHub
<#303 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGQRS7QLC5VWHAJ5IRJ3TJTZKP33PAVCNFSM6AAAAABHNJJ2XOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBWGA3TMOJVGM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
stop sending me these letters, someone made a mistake with my email, delete
the newsletter, I don’t need it
Ср, 3 июля 2024 г. в 16:28, Дмитрий Киселев ***@***.***
…:
Перестаньте мне присылать письма и удалите мой аккаунт, я не нуждаюсь в
этой рассылке …
Ср, 3 июля 2024 г. в 16:27, Loïc Jaquemet ***@***.***>:
> @ccoffin <https://github.com/ccoffin> sorry to jump into this old merged
> PR
> Would you remember why you merged this CVSS v4 schema change from
> multipleOf to enum scores in 84a2b1e
> <84a2b1e>
> ?
>
> Was that a solution to avoid validation errors in python tooling?
>
> see RedHatProductSecurity/cvelib#87
> <RedHatProductSecurity/cvelib#87> for a
> related issue+solution (load json float as decimal instead of floats).
>
> —
> Reply to this email directly, view it on GitHub
> <#303 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BGQRS7QLC5VWHAJ5IRJ3TJTZKP33PAVCNFSM6AAAAABHNJJ2XOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBWGA3TMOJVGM>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
|
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.
Includes needed updates for 5.1.0 release, new cve-schema directory structure, and new names for schema files consistent with the record format naming.