This message covers changes in this release. The complete change log can be found at Change Log | Datomic . To download this release see Datomic Pro Releases | Datomic
1.0.7705: 2026/07/10
- Feature: Permanently discontinue maintenance of a composite tuple attribute. Run upgrade-schema to get access. See Discontinuing Composite Tuples for more details.
- Upgrade: Datomic now requires Java 17 or greater.
- Upgrade: Datomic now supports Java 25. Two benign warnings may appear: a sun.misc.Unsafe deprecation on Peers and Transactors (suppress with –sun-misc-unsafe-memory-access=allow) and a restricted java.lang.System method on Peers (suppress with –enable-native-access=ALL-UNNAMED).
- Upgrade: Datomic now supports ZGC on Java 25.
- Upgrade: Datomic now requires SLF4J 2.0.17. Minimum versions for other logging deps have also been updated, please see Configuring Logging for specifics.
- Performance: improved index read performance.
- Fix: prevent blanks
(_)from unifying across function clauses in query. - Fix: SQL protocol connection map :factory parameter now works properly.
We want to draw attention to the fact that once you have used a base schema feature in a particular database (including by creating a DB on the supporting transactor version), do not run any peer or transactor process on versions of Datomic older than the features used. This directly applies to the new tuple discontinue feature included in this release. Check out this table in our docs: Datomic Deployment | Datomic