chore: version bump to allow ai-bom extension to use depgraphs #5912
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.
What does this PR do?
We recently introduced changes in cli-extension-aibom (in this PR) and in code-client-go (in this PR) that allow the aibom cli-extension to use depgraphs as part of the resulting BOM.
This PR aims to bump the corresponding versions in
go.mod
so they can be used by the CLI. Risk level should be minimal as this does not modify any existing behavior, just adds new one.DO NOT MERGE until PR#876 has been merge in snyk-ls and thego.mod
version has been bumped accordingly.The PR has been merged, and snyk-ls version has been bumped as part of this PR (notably, this means that the PR now also includes the previously mentioned change).
How should this be manually tested?
Run
make build
inside the CLI, then inside a python repo run/home/buru/work/cli/binary-releases/snyk-linux aibom --experimental
. If there are any AI packages, they should have a version next to them in the output (e.g.pkg:[email protected]
).What's the product update that needs to be communicated to CLI users?
None as of yet (we will handle all communication once the aibom extension is released to the public).
What are the relevant tickets?
See AIBOM-42 and AIBOM-55.