ci: smoke-test the task with the oldest supported sysdig-cli-scanner - #21
Merged
Merged
Conversation
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 task lets users pin
sysdigCliScannerVersion, but CI only ever ran withlatest, so nothing proved older supported versions still work with the task.The smoke run now runs the task twice: once with
latestand once with the oldest release inside the 365-day support window. The versions in the README and pipeline are tagged with markers and refreshed byjust update(update-cli-scanner/update-oldest-cli-scanner), the same approach used in scan-action and the Jenkins plugin. The dev shell now ships GNU coreutils/sed/grep because the recipes rely on them.