This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-08
Channels
- # babashka (9)
- # beginners (43)
- # biff (4)
- # calva (11)
- # cider (6)
- # clerk (1)
- # clj-kondo (4)
- # cljs-dev (6)
- # clojure (82)
- # clojure-berlin (1)
- # clojure-europe (42)
- # clojure-nl (1)
- # clojure-norway (182)
- # clojure-quebec (1)
- # clojure-uk (19)
- # clojurescript (6)
- # datahike (1)
- # emacs (30)
- # fulcro (5)
- # honeysql (6)
- # hyperfiddle (12)
- # lambdaisland (8)
- # malli (11)
- # off-topic (36)
- # pathom (26)
- # pedestal (1)
- # portal (25)
- # practicalli (1)
- # rdf (29)
- # re-frame (17)
- # reitit (1)
- # releases (1)
- # sci (37)
- # shadow-cljs (15)
- # vim (10)
- # xtdb (13)
@dnolen @mfikes fyi, the old build box is now dead. I have added a new github action that should mimic the old build box release job at https://github.com/clojure/clojurescript/actions/workflows/release.yml - you can trigger it there on demand. I haven't tested it because I didn't want to make a release but it is based on things that are working in other projects so I think it should work. happy to support whenever you next make a release
Hrm it failed because there isn't a pom.xml
file? https://github.com/clojure/clojurescript/actions/runs/5491201005/jobs/10007501347
These Clojurescript builds are not in a good state right now and the failures you see there are from various experiments I was doing. I’ve got some in process stuff locally - the pom in the cljs build is all kinds of old. I’m actually on vacation atm and won’t be back at a computer till week after next
I am still working on the equivalent of the google closure library build action