cljs-dev 2025-04-17

@alexmiller tried to release Google Closure Libary earlier - but PGP signing of the artifacts failed https://github.com/clojure/cljs.tools.closure/actions/runs/14515666560/job/40724065556

yeah the ones yesterday didn't work - I reverted a breaking change that Google introduced, can we release the new jars?

Alex Miller (Clojure team) 2025-04-18T13:49:38.327339Z

Yeah, will do in a bit

Alex Miller (Clojure team) 2025-04-18T15:51:33.118709Z

ok, out there. made a few stabs towards the auto-release, we can see if that works next time

great, thanks

tried to cut a CLJS release this morning but it failed - https://github.com/clojure/clojurescript/actions/runs/14617344743/job/41008494982 - it's probably something simple, probably due to the JDK version change

Jarrod Taylor (Clojure team) 2025-04-23T12:42:45.491239Z

I’ll take a look in just a bit.

Alex Miller (Clojure team) 2025-04-23T12:53:18.850469Z

What was the JDK change?

Closure needs 21

Jarrod Taylor (Clojure team) 2025-04-23T19:25:23.546819Z

The build is fixed and has run successfully. https://repo.maven.apache.org/maven2/org/clojure/clojurescript/1.12.35/

🎉 1
Alex Miller (Clojure team) 2025-04-17T14:42:42.326429Z

will take a look

Jarrod Taylor (Clojure team) 2025-04-17T17:25:30.145369Z

@dnolen, the github action has been mended and run successfully.

awesome thanks

Alex Miller (Clojure team) 2025-04-17T17:57:13.587479Z

I don't see the libs out there though, not sure if that's because maven or us

Alex Miller (Clojure team) 2025-04-17T18:02:36.881939Z

I did actually need to manually release these on sonatype. we really should clean this stuff up, there's no reason for that now unless it's important for you to test against the staged release for some reason @dnolen

probably wouldn't use it that much, feel free to remove that step

well probably more accurate to say we've never used it in the past!

Alex Miller (Clojure team) 2025-04-17T20:54:29.993949Z

the jars are out there now btw