Skip to content

Release v0.2.1 (dependency CVEs + container build) - #78

Merged
an1ndra merged 1 commit into
mainfrom
Develop
Nov 17, 2026
Merged

an1ndra merged 1 commit into
mainfrom
Develop

Conversation

@an1ndra

@an1ndra an1ndra commented Nov 17, 2026

Copy link
Copy Markdown
Owner

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 verify passes locally
  • python3 tools/smoke_test.py passes against tools/mock-upstream.py
  • New behaviour is covered by a test (unit or smoke)
  • The matching file in docs/ updated if an endpoint, config key or field changed
  • No credentials, .env files or data/ contents included

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.
@github-actions

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@an1ndra
an1ndra merged commit c61b4b5 into main Nov 17, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant