| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| 1.19.1 and 1.19.1-beta29_ published in error, do not use source code.tar.gz | 2026-09-07 | 14.0 MB | |
| 1.19.1 and 1.19.1-beta29_ published in error, do not use source code.zip | 2026-09-07 | 17.2 MB | |
| README.md | 2026-09-07 | 1.8 kB | |
| Totals: 3 Items | 31.3 MB | 0 | |
[!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" to1.19.2.1.19.2is numerically higher but contains less code — it is the real1.19.0+ backports, while1.19.1accidentally shipped everything up to and beyond1.20.0. Moving1.19.1 → 1.19.2would silently remove ~108 commits of functionality from your build. Go to1.20.0or 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.
