I suspect that is, in part, due to freely-available CI being a relatively recent phenomenon so a lot of Clojure projects got started before the machinery was widely available?
Also, documentation around Leiningen talks about running
lein deploy clojars (manually) but doesn’t talk about how to do it on CircleCI or GitHub Actions (the latter being an even more recent development).
In addition, many projects don’t publish snapshots anyway so having CI publish them is just not something every project maintainer wants to do (I rarely publish snapshots of my OSS projects because I don’t want to encourage folks to depend on them – especially since, with the CLI/
deps.edn, folks can depend on a
:sha to pull any version directly from GitHub).
And I guess that brings us full circle to one of the driving ideas behind some of what
tools.deps.alpha brings to the table: the ability to depend on local and git versions of projects without needing artifacts published to a third-party location. Rich has talked about the potential problems with versioned artifacts in Spec-ulation (transcript) and I think Alex Miller has also given a conference talk that touches on some that…