chore: bump sysdig-cli-scanner to 1.30.1 and automate it in just update - #48
Merged
Merged
Conversation
mateobur
previously approved these changes
Sep 24, 2026
mateobur
previously approved these changes
Sep 24, 2026
mateobur
approved these changes
Sep 24, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The CLI scanner version was hardcoded and only bumped by hand, so it drifted behind (1.23.0 while 1.30.1 is out).
just updatenow also runs a newjust update-cli-scannerrecipe that pullslatest_version.txtand rewrites the lines tagged withnewest-version-marker, the same approach used in scan-action and the Jenkins plugin.curlandsdare added to the dev shell for it.This PR also bumps the scanner to 1.30.1.
Newer scanners report package types the LSP didn't know (
oci,Software Runtimefor runtimes like Node or Rust). The package type enum rejected them, so deserialization failed for the whole report and those image scans broke. Both are now supported package types.