Fork me on GitHub
#clojars
<
2023-03-14
>
serioga19:03:00

> If you want to include pre-releases and snapshots, use the following markdown code what exactly is considered as pre-release in badge URL code? I cannot find documentation about this For example this version https://clojars.org/com.github.strojure/ring-lib/versions/1.2.0-44-alpha1 is shown on both badges. Should I deploy alpha version to snapshot server to exclude it from not pre-release badge?

tcrawley11:03:44

> what exactly is considered as pre-release in badge URL code? The Clojars code only considers snapshots as pre-release based on this query: https://github.com/clojars/clojars-web/blob/main/resources/queries/queryfile.sql#L468-L472 That drives two values in the API that http://shields.io calls: • latest_release the most recent non-snapshot version • latest_version the most recent version, snapshot or not Looking at the http://shields.io implementation, it uses latest_version for this badge, and uses latest_release to power the other badge (falling back to latest_version if latest_release isn't set, which is questionable): https://github.com/badges/shields/blob/master/services/clojars/clojars-version.service.js#L41-L47 So that wording is definitely wrong on clojars, and should just be: "If you want to include pre-releases and snapshots, use the following markdown code" > Should I deploy alpha version to snapshot server to exclude it from not pre-release badge? There is not a separate snapshot server/repo; snapshots and non-snapshots share the repo.

2