Skip to content

build(deps): langchain4j 1.20.0, and correct the log4j pin's rationale #419

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.

Sign up for GitHub

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

Merged
bernardladenthin merged 2 commits into from
Sep 5, 2026
+18 −10
Merged

build(deps): langchain4j 1.20.0, and correct the log4j pin's rationale #419

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b229f52
docs(build): the log4j pin is a floor guard now, not an active CVE fix
claude Sep 5, 2026
57b1e5b
build(deps): upgrade langchain4j from 1.19.0 to 1.20.0
claude Sep 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion llama-langchain4j/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ SPDX-License-Identifier: MIT
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<!-- langchain4j 1.x requires Java 17; the core net.ladenthin:llama stays Java 8. -->
<maven.compiler.release>17</maven.compiler.release>
<langchain4j.version>1.19.0</langchain4j.version>
<langchain4j.version>1.20.0</langchain4j.version>
<junit.version>6.1.3</junit.version>
<hamcrest.version>3.0</hamcrest.version>
<!-- Plugin versions are kept in lockstep with the core pom.xml. This module has no
Expand Down
26 changes: 17 additions & 9 deletions llama/pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,11 +74,18 @@ SPDX-License-Identifier: MIT
<jcstress.version>0.16</jcstress.version>
<lincheck.version>3.7</lincheck.version>
<logcaptor.version>2.12.7</logcaptor.version>
<!-- log4j-api / log4j-to-slf4j arrive ONLY as test-scope transitives of
io.github.hakky54:logcaptor, which requests 2.25.3. That version is affected by
CVE-2026-49844 (GHSA-qv9r-c865-cp47, moderate): MapMessage.asJson() emits bare
NaN/Infinity tokens for non-finite floats, producing non-RFC-8259 JSON. Pinned to the
newest patched stable so the alert clears; see the dependencyManagement entries. -->
<!-- FLOOR GUARD, no longer an active fix. log4j-api / log4j-to-slf4j arrive ONLY as
test-scope transitives of io.github.hakky54:logcaptor. When this pin was added,
logcaptor 2.12.6 requested log4j 2.25.3, affected by CVE-2026-49844
(GHSA-qv9r-c865-cp47, moderate): MapMessage.asJson() emits bare NaN/Infinity
tokens for non-finite floats, producing non-RFC-8259 JSON.
logcaptor 2.12.7 declares <version.log4j>2.26.1</version.log4j> itself, i.e.
exactly what this pin forces, so today it changes nothing about the resolved
graph. It is kept as a lower bound: if logcaptor ever falls back to an affected
line, the pin holds the version here instead of letting it regress silently.
Unrelated to the Java 8 class-file floor, which is a different change entirely
(slf4j-simple instead of logback, checker-qual at provided scope). Neither log4j
artifact reaches a published artifact at all; both are test scope. -->
<log4j.version>2.26.1</log4j.version>
<vmlens.version>1.2.28</vmlens.version>
<!-- DO NOT UPGRADE jqwik past 1.9.3. jqwik 1.10.0 added a deliberate
Expand Down Expand Up @@ -133,10 +140,11 @@ SPDX-License-Identifier: MIT
<artifactId>logback-classic</artifactId>
<version>${logback.version}</version>
</dependency>
<!-- log4j-api + log4j-to-slf4j: io.github.hakky54:logcaptor (test scope) brings 2.25.3,
which is affected by CVE-2026-49844; we declare ${log4j.version} directly. Both are
pinned together because log4j-to-slf4j depends on log4j-api of the same version and
the two must not skew. Test-scope only — neither reaches a published artifact. -->
<!-- log4j-api + log4j-to-slf4j, pinned as a lower bound rather than as a fix: the
logcaptor version in use already requests ${log4j.version} itself. Rationale and
the CVE history are on the property declaration above. Both are pinned together
because log4j-to-slf4j depends on log4j-api of the same version and the two must
not skew. Test-scope only — neither reaches a published artifact. -->
<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-api</artifactId>
Expand Down
Loading