I wonder if Clojars releases take some time to propagate to lein, or if perhaps there is some caching going on:

~ $ rm -rf ~/.m2/repository/nedap-lib ~/aaa; lein new nedap-lib aaa
Retrieving nedap-lib/lein-template/0.2.0-alpha2/lein-template-0.2.0-alpha2.pom from clojars
Retrieving nedap-lib/lein-template/0.2.0-alpha2/lein-template-0.2.0-alpha2.jar from clojars
~ $ rm -rf ~/.m2/repository/nedap-lib ~/aaa; lein new nedap-lib aaa
Retrieving nedap-lib/lein-template/0.2.0-alpha2/lein-template-0.2.0-alpha2.pom from clojars
Retrieving nedap-lib/lein-template/0.2.0-alpha2/lein-template-0.2.0-alpha2.jar from clojars
~ $ rm -rf ~/.m2/repository/nedap-lib ~/aaa; lein new nedap-lib aaa
Retrieving nedap-lib/lein-template/0.2.0-alpha2/lein-template-0.2.0-alpha2.pom from clojars
Retrieving nedap-lib/lein-template/0.2.0-alpha2/lein-template-0.2.0-alpha2.jar from clojars
~ $ rm -rf ~/.m2/repository/nedap-lib ~/aaa; lein new nedap-lib aaa
Retrieving nedap-lib/lein-template/0.2.0-alpha3/lein-template-0.2.0-alpha3.pom from clojars
Retrieving nedap-lib/lein-template/0.2.0-alpha3/lein-template-0.2.0-alpha3.jar from clojars

it took me 4 attempts across 10 minutes to get the alpha3 release fetched, even though it existed since the first moment

Yes, there can be up to a 15 minute delay there, since there is a CDN with a timeout, and I assume lein new will download the latest released version, which it determines by pulling the maven-metadata.xml file to get the list of versions

is the CDN. will hit the server directly, so will not have that delay.

thanks! the cache part makes sense however, I tried again and I still had to rm even 20 minutes after a new release so they are kind of different concerns... seems a fault in lein new

I may not be properly remembering the TTL - it could be longer