Trivy: Account for non existing latest/ track - #1441
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the Trivy GitHub Actions workflow to scan MicroCloud snap tracks using explicit branch names instead of relying on a latest/* snap track that MicroCloud does not publish.
Changes:
- Replaces the snap scan matrix from string versions (
latest,2) to track/branch pairs. - Updates checkout ref selection and SARIF naming to use the configured branch.
- Updates snap download channel selection to use the configured track number.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
In MicroCloud we don't use latest/ track but instead only track numbers. Only latest/edge get populated. Signed-off-by: Julian Pelizäus <julian.pelizaeus@canonical.com>
a2de581 to
0e23a20
Compare
simondeziel
left a comment
simondeziel
left a comment
There was a problem hiding this comment.
I think in LXD we should start using 6 everywhere latest is used. This should simplify aligning both sides.
If this is passing here, I can create a PR on LXD if you like. |
That would be much appreciated, thank you! |
In MicroCloud we don't use latest/ track but instead only track numbers.
Only latest/edge get populated.
I have reverted some of the changes in #1440 as its easier to carry the branch name as MicroCloud doesn't publish
latest/stable.