This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-05
Channels
- # announcements (7)
- # babashka (20)
- # beginners (130)
- # bristol-clojurians (1)
- # cider (14)
- # clj-kondo (7)
- # cljdoc (14)
- # cljs-dev (15)
- # cljsrn (16)
- # clojars (11)
- # clojure (190)
- # clojure-dev (4)
- # clojure-europe (7)
- # clojure-italy (9)
- # clojure-nl (3)
- # clojure-romania (6)
- # clojure-uk (51)
- # clojurescript (44)
- # component (4)
- # conjure (28)
- # cursive (1)
- # data-science (4)
- # datascript (1)
- # datomic (30)
- # duct (4)
- # emacs (1)
- # figwheel (4)
- # fulcro (56)
- # graalvm (4)
- # helix (51)
- # jackdaw (2)
- # jobs-discuss (12)
- # joker (4)
- # lambdaisland (1)
- # local-first-clojure (1)
- # meander (73)
- # mid-cities-meetup (2)
- # nrepl (4)
- # off-topic (43)
- # pathom (56)
- # re-frame (37)
- # reagent (26)
- # shadow-cljs (161)
- # slack-help (9)
- # spacemacs (1)
- # tools-deps (18)
- # xtdb (18)
@miikka Yep! We just released that on Sunday. It was a soft release announced to clojars-maintainers@ to test it out before wider announcement: https://groups.google.com/d/msg/clojars-maintainers/nqV5yc-05BI/-M-ci74CBgAJ. Let me know if you have any issues with it.
I just did a spec-tools release with them and it worked great, so that's a good start at least.
Also, thanks for spec-tools - we use data-specs quite a bit at http://clubhouse.io :)
A cool extra feature would be if you could restrict deploy tokens to a single artifact
But haven't captured that anywhere. Would you mind creating an issue for that at https://github.com/clojars/clojars-web/issues?