Release 1.1.0#12
Merged
Merged
Conversation
Set allWarningsAsErrors=true for the five library modules + example-rag (the ktlint/detekt-gated set), so every Kotlin warning — deprecations included — fails the build. A clean build after the dependency-upgrade wave (Spring Boot 4.1 / Spring AI 2.0 / Gradle 9.6.1 / Kotlin 2.4.10 / langchain4j 1.18 / kotest 6.2.2) reported 0 Kotlin warnings; this locks that in. benchmarks is excluded (JMH-generated sources).
Bump 1.0.0 -> 1.1.0. Promote the Spring AI 2.0 / Spring Boot 4.1 adapter-baseline change from [Unreleased] into [1.1.0]; document the LangChain4j 1.18 bump, the toolchain updates (Kotlin 2.4.10, Gradle 9.6.1, kotest 6.2.2) and the allWarningsAsErrors hardening. Sync the README status + install coordinate and the ROADMAP current-version section.
tonytonycoder11
changed the title
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
1 participant
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.
Release 1.1.0
A maintenance & compatibility release on top of
1.0.0. Kdrant's own public API is unchanged (the*.apidumps are identical,apiCheckgreen) — this release moves the framework adapters to the currentgeneration, refreshes the toolchain, and hardens the build against future deprecations.
Changed
kdrant-spring-ai→ Spring AI2.0(was1.0) andkdrant-spring-boot-starter→ Spring Boot4.1(was3.4, i.e. Spring Framework 7 / Jakarta EE 11). Verified end-to-end: the starter'sauto-configuration loads in a Boot 4 context and the
VectorStoreadapter passes its tests against SpringAI 2.0.
Compatibility: applications still on Spring AI 1.x / Spring Boot 3.x should pin those two modules to
1.0.0until they upgrade.kdrant-coreandkdrant-transport-restare unaffected.kdrant-langchain4j→ LangChain4j1.18.0(was1.0.0) — a backwards-compatible minor upgrade.Internal / quality
2.4.10, Gradle9.6.1, kotest6.2.2, plus assorted minor/patch bumps;CI actions run on Node 24.
allWarningsAsErrorsis now enabled for the five library modules +example-rag: every Kotlincompiler warning — deprecations included — fails the build, so the code stays warning-clean across future
upgrades. A full
clean build --warning-mode allreports 0 Kotlin warnings. (benchmarksis excluded— its JMH-generated sources aren't part of the standard build.)
Verified
./gradlew clean buildgreen on Gradle 9.6.1 / Kotlin 2.4.10; the full CI matrix (JDK 17/21 + Qdrantv1.18.2/latestintegration + ktlint/detekt/apiCheck) passes.After merge
Tag
v1.1.0onmainto trigger the dual-publish (Maven Central + GitHub Packages), then click Publish onthe Sonatype Central Portal.
Contains the two commits:
allWarningsAsErrorshardening + the1.1.0version/CHANGELOG/docs bump.