You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering if it's possible to provide a new project version when uploading an SBOM.
I'm not really a JS dev, but when looking into the action code, it looks like the projectVersion is only used in tandem with the projectName to know which name/version pair to upload the BOM to.
I'm imagining a scenario where I already know the project UUID, and I would like to upload a new BOM and bump the version, so that I can trace back to the exact state of the code in which Dependency Track identified a vulnerability.
Thanks for any info/hints you may have of how to solve this use-case.
The text was updated successfully, but these errors were encountered:
Hello community,
I was wondering if it's possible to provide a new project version when uploading an SBOM.
I'm not really a JS dev, but when looking into the action code, it looks like the
projectVersion
is only used in tandem with theprojectName
to know which name/version pair to upload the BOM to.I'm imagining a scenario where I already know the project UUID, and I would like to upload a new BOM and bump the version, so that I can trace back to the exact state of the code in which Dependency Track identified a vulnerability.
Thanks for any info/hints you may have of how to solve this use-case.
The text was updated successfully, but these errors were encountered: