This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-11
Channels
- # announcements (8)
- # beginners (17)
- # boot (1)
- # cider (20)
- # cljdoc (7)
- # cljs-dev (14)
- # clojure (62)
- # clojure-dev (16)
- # clojure-hamburg (1)
- # clojure-russia (2)
- # clojure-spec (22)
- # clojure-uk (15)
- # clojurebridge (1)
- # clojurescript (23)
- # core-async (4)
- # core-logic (17)
- # cursive (2)
- # datomic (4)
- # duct (1)
- # figwheel-main (40)
- # fulcro (15)
- # leiningen (1)
- # off-topic (27)
- # re-frame (3)
- # shadow-cljs (9)
- # specter (3)
- # sql (59)
Fucro 2.6.0-RC6 is now available on clojars. This rounds out the new React 16+ lifecycle support, a rework of the rendering for better React 16+ compatibility, and a few bug fixes. https://github.com/fulcrologic/fulcro
I'd like to get Clojure(Script) open-source maintainers thinking about fully automating the release processes for their projects, so here's a blog post about it: https://quanttype.net/posts/2018-08-11-fully-automated-releases.html
I’d love to see that being more of a thing. I’m wondering: with fully automated releases how would you tag releases in git or otherwise mark revisions? Would CI push that info back into your git repo?
^ i can see this integrating with something like lein-v
which allows uniquely identifying non-release builds
https://github.com/roomkey/lein-v
the nice thing about the approach with lein-v is that it decouples releasing from versioning information Benefits of lein-v: - You don't need to give your build system git write access - You avoid having noisy version bump commits in your code (because it's driven from git tags)
I'm kinda automating my releases, publishing a -SNAPSHOT release every merge to master and publishing a version every tag...
But I'm not using lein-v (yet? Maybe?)