Skip to content

Drivine 0.5.0 - #179

Merged
jasperblues merged 1 commit into
mainfrom
drivine-4j-0.5.0
Nov 6, 2026
Merged

jasperblues merged 1 commit into
mainfrom
drivine-4j-0.5.0

Conversation

@jasperblues

Copy link
Copy Markdown
Contributor

Moves Drivine from 0.4.1 to 0.5.0 (v0.5.0, train 2026.11.1):

  • pom.xml: drivine.version 0.4.1 to 0.5.0 (dice-storage uses drivine4j-spring-boot-starter).
  • dice-storage/codegen-gradle/build.gradle.kts: the standalone fallback for drivineVersion 0.4.1 to 0.5.0 (the Maven build passes -PdrivineVersion).
  • CHANGELOG.md: an Unreleased entry, Compatibility: behavioral, as for 0.4.1.

No source changes.

Binary compatibility (0.4.1 to 0.5.0)

Checked against the released jars on Maven Central.

  • drivine4j-spring, drivine4j-spring-boot-starter, drivine4j-codegen, drivine4j-codegen-java and drivine4j-coroutines are byte-identical between 0.4.1 and 0.5.0. drivine4j-codegen-model differs only in its version properties file. Their poms differ only in the version. Drivine's dependencies are unchanged (Jackson BOM still 2.19.2).
  • In drivine4j, no class is removed. A descriptor-level javap -protected -s diff finds 18 public or protected members removed or changed, all in Drivine's Cypher-to-SQL internals: the constructor, copy and copy$default of CompiledCypher (it gains a defaulted nonFinite parameter), the constructors of OracleCypherCompiler, OracleTemporalSql, Temporals, SqlCypherCompiler.Select and SqlCypherCompiler.Companion.Texts, the constants PostgresCypherCompiler.CODE_POINT_PREFIX/EXP_UNDERFLOW/MOST_PLACES/NUMERIC_TEXT/PROPERTY_READ and SqlCypherCompiler.DOOMED, and JdbcResultMapper.rows/sqliteRows. The 237 added members are in the same compilers and backends, plus Bm25. Nothing in manager, annotation, schema, query, connection (bar JdbcConnection internals), model or test changes signature.
  • None of those members is called by embabel-agent-rag-graph, embabel-chat-store or dice-storage. javap -v on their current snapshots, built on 0.4.1 (embabel-agent-rag-graph 0.6.0-20261102.070924-19, embabel-chat-store 0.7.0-20261105.174107-66, dice-storage 0.5.0-20261105.174419-65, and both autoconfigure modules), finds no reference to a removed member, and every org/drivine reference they make resolves in 0.5.0 as it did in 0.4.1. The Drivine starter, Spring, coroutines and codegen 0.4.1 jars make no such reference either.

So 0.5.0 is a drop-in for code built on 0.4.1, and each project can move on its own: no lockstep between embabel-agent-rag-graph, embabel-chat-store, dice, me and guide.

Behaviour changes in 0.5.0

Built and tested

./mvnw -U -B test verify (CI's command), with Testcontainers on the test box: all ten modules pass, 0 failures, 0 errors, 0 skipped. dice-metamodel 308 tests, dice 1763, dice-storage 492, dice-storage-autoconfigure 76, dice-report 21, dice-ingestion 8, dice-mcp-autoconfigure 20, dice-integration-tests 12. KSP codegen ran on 0.5.0; dependency:tree shows only 0.5.0 Drivine artifacts.

None of the behaviour changes fails a test here.

🤖 Generated with Claude Code

Moves Drivine from 0.4.1 to 0.5.0, and sets dice-storage's codegen
subproject's standalone fallback to the same version. 0.5.0 links with
dice-storage built on 0.4.1, so this needs no lockstep with
embabel-chat-store or embabel-agent-rag-graph.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jasperblues
jasperblues merged commit f107a45 into main Nov 6, 2026
13 checks passed
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.

1 participant