Skip to content

Update langchain4j monorepo to v1 - #41

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-langchain4j-monorepo
Open

Update langchain4j monorepo to v1#41
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-langchain4j-monorepo

Conversation

@renovate

@renovate renovate Bot commented Aug 10, 2025

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
dev.langchain4j:langchain4j-open-ai (source) 0.32.01.20.0 age confidence
dev.langchain4j:langchain4j (source) 0.32.01.20.0 age confidence

Release Notes

langchain4j/langchain4j (dev.langchain4j:langchain4j-open-ai)

v1.20.0: and 1.20.0-beta30

Compare Source

Notable Changes

Non-blocking / reactive support by @​dliubarskyi in #​5527

An AI Service method used to hold its thread for the whole interaction - the model call, tool execution, memory I/O and guardrails. It can now return CompletableFuture<T>/CompletionStage<T> for a single response, or Flow.Publisher<AiServiceStreamingEvent>/Flow.Publisher<String> for streaming, and the interaction runs without blocking a thread. You choose the mode by the method's return type; nothing else about the interface changes.

Non-blocking goes all the way down, because a blocking gap at any layer re-blocks the whole call: tool calling (sync and CompletableFuture tools, sequential or concurrent), chat memory, guardrails, and the full retrieval graph including EmbeddingModel, EmbeddingStore, ScoringModel and WebSearchEngine.

The work is additive and marked @Experimental: the synchronous and TokenStream APIs are untouched. A few defaults deliberately differ on the async path - multiple tool calls run concurrently, a tool execution error fails the invocation rather than being sent to the LLM, and a tool argument-parse error is sent to the LLM rather than failing. See Non-blocking and Reactive.

Jackson 3 opt-in support by @​dliubarskyi in #​6184

Add langchain4j-jackson3 to your classpath and LangChain4j's JSON runs on Jackson 3. There is nothing to configure and no API to call, and removing the dependency puts everything back on Jackson 2. Nothing changes for anyone who does not opt in.

With the opt-in in place, Jackson 2 can be excluded outright from most of the dependency graph; the modules that still need it are listed in the documentation. The one deliberate behaviour change is that a JSON failure surfaces as JsonReadException or JsonWriteException (both LangChain4jException) instead of a RuntimeException wrapping Jackson's own - catching RuntimeException works either way. See Using Jackson 3.

Other Changes

New Contributors

Full Changelog: langchain4j/langchain4j@1.19.0...1.20.0

v1.19.2: and 1.19.2-beta29

Compare Source

What's Changed

Full Changelog: langchain4j/langchain4j@1.19.0...1.19.2

v1.19.1: and 1.19.1-beta29: published in error, do not use

Compare Source

[!WARNING]
This release was published by mistake. Do not use it.

It was cut from main instead of release/1.19.x. Despite the version number, it is not a patch on top of 1.19.0: it contains all of 1.20.0 plus three commits that landed after it — 108 commits and 300 files ahead of 1.19.0.

Maven Central is immutable, so these artifacts cannot be withdrawn. This note is the only way we can flag them.

Which version should I use?

If you are on Use Why
1.19.0 or earlier, and want to stay on the 1.19.x line 1.19.2 The intended patch: 1.19.0 + the MCP backports
1.19.1 1.20.0 or later See the warning below
anything else 1.20.0 Current release

[!CAUTION]
If you are already on 1.19.1, do not "upgrade" to 1.19.2.
1.19.2 is numerically higher but contains less code — it is the real 1.19.0 + backports, while 1.19.1 accidentally shipped everything up to and beyond 1.20.0. Moving 1.19.1 → 1.19.2 would silently remove ~108 commits of functionality from your build. Go to 1.20.0 or later instead.

What replaced it

1.19.2 / 1.19.2-beta29 is the patch that 1.19.1 was meant to be: 1.19.0 plus the MCP backports from #​6329, and nothing else.

Also affected

langchain4j-spring 1.19.1-beta29 was published from the same faulty run and carries the same warning. Use 1.19.2-beta29 or 1.20.0-beta30.

Note for anyone comparing APIs

Because 1.19.1 sits between 1.19.0 and 1.20.0 in version order while containing post-1.20.0 code, tools that pick "the newest release below X" as a baseline (revapi's oldVersion=RELEASE, among others) will select it and report misleading API differences for any 1.19.x build.

v1.19.0: and 1.19.0-beta29

Compare Source

Notable Changes
Other Changes
New Contributors
  • [@​OmkarKathi

Important

✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from fa800bd to 91c1cc8 Compare August 28, 2025 16:52
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from 91c1cc8 to da963da Compare September 16, 2025 15:54
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch 3 times, most recently from 3ae2dae to 9942f99 Compare October 2, 2025 17:12
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from 9942f99 to 75b04b3 Compare October 24, 2025 20:12
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch 2 times, most recently from 6daac13 to e6eec06 Compare November 28, 2025 13:48
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from e6eec06 to 350d905 Compare December 24, 2025 17:38
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from 350d905 to 05e9c1f Compare February 4, 2026 12:39
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch 2 times, most recently from e3afcfb to f169b58 Compare March 6, 2026 22:40
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from f169b58 to 1e059f1 Compare April 9, 2026 14:11
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from 1e059f1 to 5949938 Compare April 22, 2026 19:59
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch 2 times, most recently from be0ca15 to 0d12449 Compare May 7, 2026 14:07
@renovate renovate Bot changed the title Update langchain4j monorepo to v1 (major) Update langchain4j monorepo to v1 May 12, 2026
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from 0d12449 to f43401c Compare May 15, 2026 17:25
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from f43401c to b1c7adf Compare May 28, 2026 19:07
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch 3 times, most recently from ac45ea3 to 0ef78e8 Compare June 10, 2026 15:58
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from 0ef78e8 to 96f9d0d Compare June 15, 2026 09:46
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch 2 times, most recently from a872fa8 to 161e5df Compare June 30, 2026 18:42
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from 161e5df to d6492ae Compare July 6, 2026 14:10
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from d6492ae to c1db3bd Compare July 17, 2026 14:12
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from c1db3bd to 483ef2f Compare July 29, 2026 17:27
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from 483ef2f to a582189 Compare August 16, 2026 02:59
@renovate
renovate Bot force-pushed the renovate/major-langchain4j-monorepo branch from a582189 to a93e774 Compare September 4, 2026 14:10
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.

0 participants