-
Notifications
You must be signed in to change notification settings - Fork 279
chore(deps): Update trivy to v0.65.0 #481
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
Conversation
6389d65
to
636fd3c
Compare
Tests are red as we need to sync the DBs. Depends on #482 |
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.
Pull Request Overview
This PR updates Trivy to version v0.65.0 across all configuration files and test data. This is a dependency update that ensures the project uses the latest version of the Trivy security scanner.
Key changes:
- Updates default Trivy version from v0.64.1 to v0.65.0 in action configuration
- Updates test data files to reflect output format changes from the new Trivy version
- Updates documentation to reference the new version
Reviewed Changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
action.yaml | Updates default Trivy version parameter from v0.64.1 to v0.65.0 |
README.md | Updates documentation examples and version references to v0.65.0 |
.github/workflows/test.yaml | Updates TRIVY_VERSION environment variable to 0.65.0 |
test/data/with-trivy-yaml-cfg/report.json | Updates test data to reflect new Trivy output format (PURL encoding and timestamp changes) |
test/data/with-ignore-files/report | Updates test data with modified CVE description formatting |
test/data/image-scan/report | Updates test data with modified CVE description formatting |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Signed-off-by: Nikita Pivkin <nikita.pivkin@smartforce.io>
Signed-off-by: Nikita Pivkin <nikita.pivkin@smartforce.io>
@simar7 I added a goal for updating golden files |
Makefile
Outdated
.PHONY: update-golden | ||
update-golden: | ||
mkdir -p .cache | ||
UPDATE_GOLDEN=1 $(BATS_ENV) bats $(BATS_FLAGS) |
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.
That's nice, should we add this target to the action that upgrades the trivy version? We would always review the PR it will create prior to merge, thereby avoiding us to run the target ourselves manually.
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.
Done a169870
(#481)
Signed-off-by: Nikita Pivkin <nikita.pivkin@smartforce.io>
Signed-off-by: Nikita Pivkin <nikita.pivkin@smartforce.io>
In general, we don't need to update the databases unless we upgrade Trivy to a version that uses new database schemas. This minimizes updates to golden files. |
Automated changes by create-pull-request GitHub action