-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(go): Do not trim v prefix from versions in Go Mod Analyzer #7733
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @DmitriyLewen, I have added the v prefix to the version numbers in the test and test-cases file for the Go Mod Analyzer so that it matches the required versioning format. Please review and suggest changes, if any. Thanks. |
You also need to update integration and k8s tests. |
@DmitriyLewen I tried running that command but it always errors out. Any suggestions on this?
|
@Rutam21 You don't have enough disk space.
If you have more space in another directory, you can specify it like |
@Rutam21 don't worry i updated golden files @knqyf263 when I updated the gold files - I thought - do we need to update the docs/other tests?
Also i thought about
|
Thank you @DmitriyLewen. Due to storage constraints, the suggested command was failing for me always. |
Yes, it would be great if the version formats are consistent in Trivy so that we will not get confused in the future.
|
@knqyf263 I updated testcases and docs. Also we need to update k8s scanner package to add
Done in d5a787b |
Thanks. GitHub Actions is down now. We'll merge this PR after it's back. |
Rebased this PR. |
@DmitriyLewen You requested changes before. Your review is blocking this PR. |
Approved |
Description
This PR modifies the Go Mod Analyzer file so that the prefix "v" is not trimmed from the versions to maintain consistency with the Go Binary Analyzer.
Related issues
v
prefix from versions #7711Checklist