Where can we find the latest deps that will cause :dependency-conflicts?
The cloud-deps.edn for ion-dev 1.0.356 still lists Jetty 9.4.53.v20231009
We want to up our deps locally, test that all is good, and then only ion-deploy.
@jaret Awesome. We are quite excited.
I still need to know where to get the Canonical Datomic Cloud Deps to stuff into our deps.edn to test for any weirdness
You were in the right place getting the clojure-deps.edn as that is what is used to understand the running environment
but it is intentionally undocumented as we might make this better in the future
Hi @danie! I think this is another flavor of the https://clojurians.slack.com/archives/C03RZMDSH/p1783522129535869?thread_ts=1782932460.416989&cid=C03RZMDSHwe are addressing. It is still true that we completely removed Jetty 9 from Datomic clients. However, the aws-api is being pulled in via core2, --we didn't realize this was on the Ions classpath until this release and a customers use of aws-api conflicting. Once we release the next Cloud release (hopefully this week) this conflict will no longer be present via Ion-dev. Apologies.