Repository navigation
Drivine 0.3.0 - #60
Merged
Merged
Conversation
Moves Drivine from 0.2.0 to 0.3.0, with embabel-agent-rag-graph and embabel-chat-store, whose snapshots move to 0.3.0 too: 0.3.0 drops the compiled constructor that a Kotlin call to UniquenessConstraintSpec with a defaulted argument links to, so the Guide on one Drivine and its libraries on the other fail at context load with NoSuchMethodError. No source changes.
jasperblues
marked this pull request as ready for review
October 26, 2026 02:55
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
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.
Moves Drivine from 0.2.0 to 0.3.0, in the pom and in
codegen-gradle/build.gradle.kts, with embabel-agent-rag-graph and embabel-chat-store.Draft until drivine4j 0.3.0 is published, and until the rag-graph and chat-store bumps are merged and their snapshots rebuilt (embabel/embabel-agent-rag-graph#72, embabel/embabel-chat-store#50). Before then CI fails: first to resolve Drivine 0.3.0, then at context load.
Why
Drivine 0.3.0 drops the compiled constructor that a Kotlin call to
UniquenessConstraintSpecwith a defaulted argument links to. The libraries the Guide uses make such calls, so the Guide on one Drivine and its libraries on the other don't link. With 0.3.0 and the libraries' current 0.2.0 snapshots, 109 of 183 tests fail at context load withNoSuchMethodErrorfrom chat-store'schatStoreConstraintSchema. Once all of them are on 0.3.0, they link.No source changes.
Tested
Against the released drivine4j 0.3.0 (tag
0.3.0), from the local Maven repository since Central doesn't serve it yet, with rag-graph 0.6.0-SNAPSHOT and chat-store 0.7.0-SNAPSHOT rebuilt on it from theirchore/drivine-0.3.0branches (embabel/embabel-agent-rag-graph#72, embabel/embabel-chat-store#50):codegen-gradle's./gradlew kspKotlingenerates the DSL against 0.3.0, andmvn installis green, 183 tests on Neo4j and Postgres in Testcontainers, 0 failures, 0 skipped. The dependency tree resolves every Drivine artifact at 0.3.0.Earlier, against drivine4j
main(2fe93c5) installed locally as 0.3.0-SNAPSHOT, the same 183 tests were green.