chore: upgrade SBOM generators #964
Conversation
There was a problem hiding this comment.
good to have this @jkowalleck , and I agree the gh action being used is not the best way to create SBOMs
did you want to fix up this workflow as well? .github/workflows/push.yaml
This comment was marked as resolved.
This comment was marked as resolved.
yep. the idea was to revisit all SBOM generation workflows and upgrade then to a modern maintained system |
jkowalleck
changed the title
|
@jgadsden upgrade done. was unable to test successfully, since some unrelated/untouched CI jobs are skipped or dont pass. feel free to merge, or ping me in case a rebase is done and changes/updates are required. |
Signed-off-by: Jan Kowalleck <[email protected]>
There was a problem hiding this comment.
thanks for applying this to all the SBOM generators @jkowalleck
going ahead with the merge because the two failing tests are known issues
|
@jgadsden i see something is off in the SBOM process. I will drop a fix soon |
Summary:
I've seen you are shipping SBOMs with every release 👍
I've seen you are using the unmaintained github workflow
CycloneDX/gh-node-module-generatebomto generate them.I propose to switch to the maintained
@cyclonedx/cyclonedx-npminstead.I propose to use
@cyclonedx/webpack-pluginfor the VueJS frontendsDescription for the changelog:
chore: upgrade SBOM generators
Other info:
fixes #963