git deps are really primarily useful for tools and dev-time deps. or for apps, if you use tools.build, they will also be pulled into an uberjar. for oss libs you expect to be consumed, I think it's best to provide an artifact.

The only git dep we depend on at runtime is a PR against net.mikera/imagez that has not been released yet -- all the other git deps are dev/build time tooling. Def. agree with Alex. If there's a specific project that you want to depend on as a library for your own library, it's worth asking the maintainer to publish a versioned artifact.

Git deps are also great for consuming libraries that are meant to be open source but are not production ready yet - I have a couple in the works, and they are available on GH, but I won't release them to Clojars until they're more battle tested, but I'd be cautious of using somebody else's library via git - there are valid reasons sometimes (unmerged PRs)