Fork me on GitHub
#cljs-dev
<
2019-02-14
>
borkdude07:02:26

If this won’t be included, I’ll just close it ;-) https://github.com/clojure/clojurescript-site/pull/300

dnolen14:02:08

@borkdude sorry just missed that merged

borkdude15:02:27

thanks for the merge

dnolen20:02:30

@alexmiller pretty sure GClosure Library deploy is not automated

dnolen20:02:54

they have to be manually released - the build in Hudson describes the procedure

Alex Miller (Clojure team)20:02:07

you know far better than me :)

dnolen20:02:38

yeah Stuart Sierra never got around to it - and I didn't either

dnolen20:02:51

new releases of GClosure Library & 3rd party should be available shortly

Alex Miller (Clojure team)21:02:50

google-closure-library 0.0-20190213-2033d5d9 google-closure-library-third-party 0.0-20190213-2033d5d9

👍 10
mfikes23:02:31

^ Our assurance that ClojureScript properly works with the latest Closure Library is the closurelib project in Canary https://github.com/cljs-oss/canary Note: Of interest is that the 1.10.439 compiler had prep work done in it https://dev.clojure.org/jira/browse/CLJS-2702 —done as part of the Cojureist Together grant—to allow it to work with changes that are in the latest Closure Library relative to what ClojureScript currently ships with. The changes affect REPLs and are now present in all of the shipping REPLs, but may or may not be in downstream REPLs.