This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-24
Channels
- # announcements (30)
- # asami (9)
- # babashka (37)
- # beginners (120)
- # calva (26)
- # cider (3)
- # clara (9)
- # clj-commons (7)
- # clj-kondo (17)
- # cljsrn (2)
- # clojure (32)
- # clojure-europe (56)
- # clojure-nl (1)
- # clojure-norway (13)
- # clojure-uk (4)
- # clojurescript (34)
- # conjure (1)
- # copenhagen-clojurians (8)
- # core-async (21)
- # cursive (2)
- # datahike (2)
- # datascript (5)
- # events (4)
- # fulcro (32)
- # graalvm (10)
- # heroku (3)
- # introduce-yourself (1)
- # jobs (2)
- # lsp (3)
- # luminus (1)
- # malli (8)
- # meander (15)
- # minecraft (1)
- # nrepl (2)
- # off-topic (57)
- # pathom (2)
- # polylith (35)
- # reagent (6)
- # reitit (8)
- # releases (1)
- # rewrite-clj (7)
- # shadow-cljs (21)
- # timbre (4)
- # tools-build (1)
- # tools-deps (33)
- # vrac (8)
Updating the circle-ci config now. All that’s needed to deploy is to push a Release-.*
tag and that will kick off a deploy-job which deploys to clojars.
This is not done for manifold et al because they deploy to the manifold
clojars org.
Thanks, I’ll try that for byte-streams
@U04V5VAUN Seeing a lot “Unauthorized” errors: https://app.circleci.com/pipelines/github/clj-commons/byte-streams I don’t think I can run the “deploy” phase
@U04V5VAUN Got a new error: https://app.circleci.com/pipelines/github/clj-commons/byte-streams/23/workflows/c3d247b7-7b14-432c-899c-b82934ee75c8/jobs/34/parallel-runs/0/steps/0-109 Something about clj-commons not being verified on clojars, so it can’t contain new groups…