-
Notifications
You must be signed in to change notification settings - Fork 9
feat(CSAF2.1): #364 add recommended test 6.2.44 #369
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
base: main
Are you sure you want to change the base?
Conversation
28723e4
to
6a94aec
Compare
Coverage after merging feat/363-csaf-2.1_recommended_test_6.2.44 into main
Coverage Report
|
LGTM |
6a94aec
to
42b3186
Compare
Coverage after merging feat/363-csaf-2.1_recommended_test_6.2.44 into main
Coverage Report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might have missed that: Where is the script to generate the license_information.js
?
Please also add some comments in the README about the update process...
Could we also add since which version the license is deprecated? 🤔
5b29009
to
a9366a7
Compare
Coverage after merging feat/363-csaf-2.1_recommended_test_6.2.44 into main
Coverage Report
|
Neither the scancode library 'https://scancode-licensedb.aboutcode.org/index.json' nor the SPDX library 'https://raw.githubusercontent.com/spdx/license-list-data/refs/heads/main/json/licenses.json' has the information about when the license became deprecated. |
a9366a7
to
9b2ad2e
Compare
Coverage after merging feat/363-csaf-2.1_recommended_test_6.2.44 into main
Coverage Report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please review my comments. Happy to discuss if needed.
deprecatedLicenseIdentifiers.forEach((licenseKey) => { | ||
ctx.warnings.push({ | ||
instancePath: '/document/license_expression', | ||
message: `License identifier ${licenseKey} is deprecated `, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm... License identifier is a fixed term. I know that you don't mean that here as also expressions can be deprecated. Therefore, I suggest to either switch to license key
or use just identifier
(without license) or come up with a better suggestion.
) { | ||
deprecatedLicenses.push(parsedExpression.exception) | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are missing the AdditionRefs
here.
Well, both live in a Git. So, we would be able to extract that information, correct? The question is, what do we store. Do both have versions in their Git (e.g. as tags)? Than, we could use the next tag as deprecation version (or a Please put that on the agenda to be discussed in the next meeting. There, please provide a suggestion how you would implement that and what the estimated time of that change would be. |
9b2ad2e
to
d585b21
Compare
Coverage after merging feat/363-csaf-2.1_recommended_test_6.2.44 into main
Coverage Report
|
…d name of variables
…rmation.js with prettier
d585b21
to
29957cd
Compare
Coverage after merging feat/363-csaf-2.1_recommended_test_6.2.44 into main
Coverage Report
|
No description provided.