This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-02-04
Channels
- # announcements (1)
- # architecture (18)
- # aws (7)
- # babashka (63)
- # beginners (38)
- # bristol-clojurians (1)
- # circleci (1)
- # clj-kondo (10)
- # clojars (4)
- # clojure (159)
- # clojure-berlin (3)
- # clojure-europe (4)
- # clojure-italy (7)
- # clojure-losangeles (6)
- # clojure-nl (7)
- # clojure-spec (3)
- # clojure-uk (109)
- # clojurescript (54)
- # css (1)
- # cursive (38)
- # data-science (2)
- # datascript (3)
- # datomic (14)
- # docker (2)
- # duct (11)
- # fulcro (47)
- # jobs (8)
- # jobs-discuss (3)
- # kaocha (4)
- # malli (3)
- # nyc (2)
- # off-topic (30)
- # overtone (3)
- # re-frame (17)
- # reagent (33)
- # shadow-cljs (29)
- # spacemacs (3)
- # specter (4)
- # tools-deps (13)
- # xtdb (13)
If I have released an alpha release, e.g. my-project "2.0.1-alpha2"
, then
will show that alpha as the most recent version, (and the one used in the Leiningen/Boot
/`Clojure CLI/deps.edn` snippets)
...while that is technically true, it can lead people to believe they are supposed to consume this alpha, when in reality it has a narrower intended target audience.
Wondering if this has been considered already?
@vemv It has! But there really hasn't been any discussion about it - https://github.com/clojars/clojars-web/issues/398
An issue is there really isn't a standard for what is or isn't a "stable" version other than a -SNAPSHOT
isn't stable. We would either need to come up with that standard or allow the user a way to signal a version as non-stable - probably through the UI.