Ion 1.0.68 and Ion-dev 1.0.316 [Datomic Cloud]

This message covers changes in this release. For more details, see Datomic Cloud Releases | Datomic

2023/12/20 1.0.68 ion

  • Upgraded aws-java-sdk-ssm to 1.12.564

2023/12/20 1.0.316 ion-dev

  • Upgraded Clojure to 1.11.1
  • Upgraded AWS Java SDK to 1.12.564
  • Upgraded org.yaml/snakeyaml to 2.2

Jaret,

As I see, the set of dependencies has been updated in the ion-dev lib:

❯ unzip -p ~/.m2/repository/com/datomic/ion-dev/1.0.316/ion-dev-1.0.316.jar datomic/ion/dev/cloud-deps.edn | jet | grep -E 'com\.datomic/client-(api|cloud)'
        com.datomic/client-api {:mvn/version "1.0.68"},
        com.datomic/client-cloud {:mvn/version "1.0.124"},

I’m still getting a bunch of dependency conflicts:

 :dependency-conflicts
 {:deps
  {com.cognitect/transit-java #:mvn{:version "1.0.371"},
   org.clojure/clojure #:mvn{:version "1.11.1"},
   org.eclipse.jetty/jetty-servlet #:mvn{:version "9.4.52.v20230823"},
   com.cognitect/http-endpoint #:mvn{:version "1.0.104"},
   com.fasterxml.jackson.core/jackson-core #:mvn{:version "2.12.3"},
   org.eclipse.jetty/jetty-security #:mvn{:version "9.4.52.v20230823"},
   org.eclipse.jetty/jetty-util-ajax
   #:mvn{:version "9.4.52.v20230823"},
   com.datomic/ion-resolver #:mvn{:version "0.9.18"},
   com.google.guava/guava #:mvn{:version "32.0.1-jre"},
   com.cognitect/transit-clj #:mvn{:version "1.0.333"},
   com.cognitect/caster #:mvn{:version "1.0.45"},
   org.slf4j/slf4j-api #:mvn{:version "1.7.36"},
   com.github.ben-manes.caffeine/caffeine #:mvn{:version "2.8.1"},
   org.eclipse.jetty/jetty-server #:mvn{:version "9.4.52.v20230823"},
   com.amazonaws/aws-java-sdk-kms #:mvn{:version "1.12.564"},
   javax.xml.bind/jaxb-api #:mvn{:version "2.4.0-b180830.0359"},
   com.amazonaws/aws-java-sdk-s3 #:mvn{:version "1.12.564"}},
  :doc
  "The :push operation overrode these dependencies to match versions already running in Datomic Cloud. To test locally, add these explicit deps to your deps.edn."},

Should I still ignore these?

Or am I doing some thing wrong, if I’ve upgraded my datomic deps already?

❯ grep -E 'com\.datomic/(ion|client)' deps.edn
  com.datomic/ion             {:mvn/version "1.0.68"}
  com.datomic/client-cloud    {:mvn/version "1.0.124"
  {:deps {com.datomic/ion-dev {:mvn/version "1.0.316"}}