> • 0.2.18-SNAPSHOT at the top. This is the current version you are viewing > • The message "Current release is 0.2.18-issue-318-02". This is the latest known non-SNAPSHOT release (and because you are previewing, this is from your local cljdoc database) > • 0.2.17-alpha in my badge, that takes it from CURRENT in the page. This draws from cljdoc production and is the current release available release on http://cljdoc.org > Questions: > • Do I need to hard code 0.2.18-SNAPSHOT in the badge instead of using CURRENT? There is currently no badge support for SNAPSHOT releases > • Where does 0.2.18-issue-318-02 come from? Is it possible to change it to 0.2.18-SNAPSHOT ? This is the latest known non-SNAPSHOT release (drawn from your locally running cljdoc in this case). And nope, no current support for SNAPSHOT release for badges. See also: https://github.com/cljdoc/cljdoc/blob/master/doc/userguide/for-library-authors.adoc#snapshot-builds The note on scm tag for SNAPSHOT builds is important and a thing folks often get wrong.

I think clojars supports snapshot badges. We could consider that for cljdoc. Could have sworn there was an issue for this already but cannot seem to locate it at the moment.

Okay, thanks. I'm setting :scm https://github.com/polyfy/polylith/blob/1c93ae1c95c4d69682b4fa6a086d5586af79b644/build.clj#L173-L177. Do you think this should be enough?

Yeah, that check seems good to me!