Repository navigation
Conversation
The v0.2.0 release job built and pushed its image, then failed at the Trivy gate with eight CRITICAL findings in the application jar: tomcat-embed-core 10.1.55 5 CVEs fixed in 10.1.62 netty-handler 4.1.135 1 CVE fixed in 4.1.141 spring-webmvc 6.2.19 2 CVEs fixed only in 7.0.9 (Spring Boot 4) Spring Boot 3.5.16 is the latest 3.5 and still pins the old tomcat and netty, so they are overridden in the pom. The two Spring CVEs have no 6.2.x fix; both live in view rendering (XsltView path handling and SSE with views) and Path registers no view resolver and renders nothing through a View, so neither path is reachable. They are listed in .trivyignore.yaml with a statement and expired_at 2027-02-01, and the release workflow now passes that file explicitly because the YAML form is not auto-detected. Verified with the same scanner and flags as the gate: 8 CRITICAL -> 0 on the 0.2.1 jar. 164 tests, 157 smoke checks. 0.2.1 rather than re-tagging 0.2.0 again: the 0.2.0 image was already pushed to GHCR, so that version has published artifacts.
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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
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 v0.2.0 release job built and pushed its image, then failed at the Trivy gate with eight CRITICAL findings in the application jar:
tomcat-embed-core 10.1.55 5 CVEs fixed in 10.1.62
netty-handler 4.1.135 1 CVE fixed in 4.1.141
spring-webmvc 6.2.19 2 CVEs fixed only in 7.0.9 (Spring Boot 4)
Spring Boot 3.5.16 is the latest 3.5 and still pins the old tomcat and netty, so they are overridden in the pom. The two Spring CVEs have no 6.2.x fix; both live in view rendering (XsltView path handling and SSE with views) and Path registers no view resolver and renders nothing through a View, so neither path is reachable. They are listed in .trivyignore.yaml with a statement and expired_at 2027-02-01, and the release workflow now passes that file explicitly because the YAML form is not auto-detected.
Verified with the same scanner and flags as the gate: 8 CRITICAL -> 0 on the 0.2.1 jar. 164 tests, 157 smoke checks.
0.2.1 rather than re-tagging 0.2.0 again: the 0.2.0 image was already pushed to GHCR, so that version has published artifacts.
What does this change?
Checklist
./mvnw verifypasses locallypython3 tools/smoke_test.pypasses againsttools/mock-upstream.pydocs/updated if an endpoint, config key or field changed.envfiles ordata/contents included