Repository navigation
[BOURNE-3137] Resolve Dependabot alerts - #36
Merged
Merged
Conversation
Resolves all open critical and high severity Dependabot alerts: - netty 4.1.130.Final -> 4.1.138.Final covers the netty-codec, netty-codec-http, and netty-codec-http2 alerts (highest patched version required by any alert was 4.1.137.Final). - pmd 7.6.0 -> 7.28.0 covers the critical pmd-core alert (patched in 7.10.0) and the medium one (patched in 7.22.0). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
chao-shawn
marked this pull request as ready for review
September 29, 2026 17:50
adhurjaty
approved these changes
Sep 29, 2026
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.
Resolves all open critical and high severity Dependabot alerts on this repo (and, as a side effect, every open
nettyandpmd-coremoderate alert too, since the patched versions are the same properties).Changes
netty.version4.1.130.Final4.1.138.Final4.1.137.Final;4.1.138.Finalis the latest 4.1.x on Maven Central.pmd.version7.6.07.28.0pmd-corealert is patched in7.10.0, the moderate one in7.22.0.Alerts addressed
Critical (1)
net.sourceforge.pmd:pmd-core(>= 6.21.0, < 7.10.0)High (11) — all
io.nettycodec artifactsnetty-codec-http2netty-codec-httpnetty-codecAlso resolved (moderate) — #28, #25, #20, #19, #18, #16, #11, #8, #7, #6, #3
Alert #1 (
org.keycloak:keycloak-core, low, incontrib/custom-representations/pom.xml) is not addressed here — it is low severity, has no patched version published, and lives in a separate contrib module. Out of scope for this PR.Verification
./mvnw compile pmd:check— passes (PMD 7.28.0 reports no new violations against the maven-pmd-plugin default ruleset; no custom ruleset in this repo)../mvnw test— 339 tests, 0 failures, 0 errors../mvnw dependency:tree -Dincludes='io.netty:*'confirmsnetty-codec,netty-codec-http, andnetty-codec-http2all resolve to4.1.138.Final.*IT, Testcontainers + Keycloak) were not run locally — leaving those to CI, which is why this is a draft.Note for reviewers
The other netty artifacts (
netty-buffer,netty-common,netty-handler,netty-transport, ...) still resolve to4.1.135.Final. That is because thekeycloak-parentBOM is imported at pom.xml:155, before thenetty-bomimport at pom.xml:217, so keycloak-parent's netty pins win for everything not explicitly listed in our owndependencyManagement. This is why the three explicitnetty-codec*entries exist at pom.xml:224-239 — they are the only way to override keycloak-parent. None of those other artifacts have open alerts, so this PR does not touch them, but it is worth knowing that thenetty-bomimport is currently shadowed and bumpingnetty.versionalone would not move them.🤖 Generated with Claude Code