Skip to content

Fix Spring JMS and Log4j security alerts - #53

Merged
milt merged 1 commit into
mainfrom
codex/fix-security-dependencies
Oct 16, 2026
Merged

milt merged 1 commit into
mainfrom
codex/fix-security-dependencies

Conversation

@milt

@milt milt commented Oct 16, 2026

Copy link
Copy Markdown
Member

Addresses the six current Dependabot alerts with version-only changes in pom.xml: updates Log4j API, Core, and SLF4J2 binding from 2.23.1 to 2.25.5, and Spring context/JMS from 6.1.21 to 6.2.19. The resolved tree confirms all Spring modules use 6.2.19 and all Log4j modules use 2.25.5. No application or documentation changes.

Validation on Java 21:

  • make verify passed: 244 tests, zero failures/errors/skips, including PostgreSQL Testcontainers coverage. Portico vendoring, shaded JAR packaging, Spotless, and Checkstyle succeeded.
  • MCP GitHub Advisory Database check reported zero findings for the five changed dependencies; this was a targeted scan, not a full dependency audit.
  • Maven dependency tree resolution and git diff --check passed.

This includes the Log4j Core fix proposed in #52 and additionally aligns the API/binding and updates Spring. Alert closure remains dependent on merging and GitHub refresh.

@milt
milt merged commit 8ee2a45 into main Oct 16, 2026
1 check passed
@milt
milt deleted the codex/fix-security-dependencies branch October 16, 2026 19:44
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