Fork me on GitHub
#announcements
<
2018-08-11
>
tony.kay06:08:31

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

miikka10:08:45

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

martinklepsch11:08:45

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?

miikka12:08:20

Yeah, exactly

rymndhng19:08:30

^ i can see this integrating with something like lein-v which allows uniquely identifying non-release builds https://github.com/roomkey/lein-v

rymndhng19:08:02

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)

mauricio.szabo20:08:20

I'm kinda automating my releases, publishing a -SNAPSHOT release every merge to master and publishing a version every tag...

mauricio.szabo20:08:39

But I'm not using lein-v (yet? Maybe?)