Find newer versions of your dependencies in your deps.edn
file using the Clojure CLI. This works for maven and git dependencies.
You can try it out easily with this one liner:
$ clojure -Sdeps '{:deps {olical/depot {:mvn/version "1.8.0"}}}' -m depot.outdated.main
| Dependency | Current | Latest |
|---------------------|---------|--------|
| org.clojure/clojure | 1.9.0 | 1.10.0 |
I'd recommend adding depot as an alias in your own deps.edn
file, this will allow it to check itself for updates:
Note: Replace the ellipsis with the current version shown above.
{:deps {}
:aliases {:outdated {:extra-deps {olical/depot {:mvn/version "..."}}
:main-opts ["-m" "depot.outdated.main"]}}}
$ clojure -Aoutdated -a outdated
| Dependency | Current | Latest |
|--------------|---------|--------|
| olical/depot | ..... | ..... |
deps.edn
To automatically update the versions in deps.edn
, use --update
.
$ clojure -m depot.outdated.main --update
Updating: deps.edn
rewrite-clj {:mvn/version "0.6.0"} -> {:mvn/version "0.6.1"}
cider/cider-nrepl {:mvn/version "0.17.0"} -> {:mvn/version "0.18.0"}
clj-time {:mvn/version "0.14.4"} -> {:mvn/version "0.15.1"}
olical/cljs-test-runner {:sha "5a18d41648d5c3a64632b5fec07734d32cca7671"} -> {:sha "da9710b389782d4637ef114176f6e741225e16f0"}
This will leave any formatting, whitespace, and comments intact. It will update
both the top level deps and any :aliases
/ :extra-deps
. To prevent Depot
from touching certain parts of your deps.edn
, mark them with the
^:depot/ignore
metadata.
{:deps {...}
:aliases
{;; used for testing against older versions of Clojure
:clojure-1.8 ^:depot/ignore {:extra-deps
{org.clojure/clojure {:mvn/version "1.8.0"}}}
:clojure-1.9 ^:depot/ignore {:extra-deps
{org.clojure/clojure {:mvn/version "1.9.0"}}}}}
--update
by default looks for deps.edn
in the current working directory. You
can instead pass one or more filenames in explicitly.
$ clojure -m depot.outdated.main --update ../my-project/deps.edn
Maven has a concept called "virtual" versions, these are similar to Git branches, they are pointers to another version, and the version they point to can change over time. The best known example are snapshot releases. When your deps.edn
refers to a version 0.4.1-SNAPSHOT
, the version that actually gets installed will look like 0.4.1-20190222.154954-1
.
A maintainer can publish as many snapshots as they like, all with the same version string. This means that re-running the same code twice might yield different results, if in the meanwhile a new snapshot was released. So installing 0.4.1-SNAPSHOT
again later on may install a completely different version.
For the sake of stability and reproducibility it may be desirable to "lock" this version. This is what the --resolve-virtual
flag is for. The --resolve-virtual
flag will replace the snapshot version with the current timestamped version that the SNAPSHOT is an alias of, so that your code is once again deterministic.
Besides SNAPSHOT
versions --resolve-virtual
will also handle the special version strings "RELEASE"
and "LATEST"
% clojure -Sdeps '{:deps {olical/depot {:local/root "/home/arne/github/depot"}}}' -m depot.outdated.main --resolve-virtual
Resolving: deps.edn
cider/piggieback 0.4.1-SNAPSHOT --> 0.4.1-20190222.154954-1
This project is inspired by lein-ancient, it relies on version-clj (by the same author, xsc) for parsing and comparison of version numbers.
:override-deps
.--update
and --resolve-virtual
systems, so many improvements!:override-deps
is adhered to in the non-mutating mode.Find the full unlicense in the UNLICENSE
file, but here's a snippet.
This is free and unencumbered software released into the public domain.
Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.
Do what you want. Learn as much as you can. Unlicense more software.
Can you improve this documentation?Edit on GitHub
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close