Investigate using semantic-release

[victorb]

Semantic Release is a project for automating package publishing. It's a nice tool to not miss to publish a new version once new changes are in and I think it would fit very well to have automated via aegir.

It does a bunch of things, maybe even too much. If so, we could maybe just integrate the publishing part while leaving out the rest, but in general, it would be nice to try to automate the publishing so in the future, it'll be easy to integrate with the CI system.

https://github.com/semantic-release/semantic-release

[dignifiedquire]

I have looked at semantic-release before, but it does quite a lot and sometimes in a way that is not the way we would like to do it. I am curious which part of it you are missing, as integrating individual functionality is much cheaper in terms of speed and dependency size and much easier development wise as the core tool was not particular modular when I checked last time.

On 30. Oct 2017, 16:22 +0100, ᴠɪᴄᴛᴏʀ ʙᴊᴇʟᴋʜᴏʟᴍ notifications@github.com, wrote:

Semantic Release is a project for automating package publishing. It's a nice tool to not miss to publish a new version once new changes are in and I think it would fit very well to have automated via aegir. It does a bunch of things, maybe even too much. If so, we could maybe just integrate the publishing part while leaving out the rest, but in general, it would be nice to try to automate the publishing so in the future, it'll be easy to integrate with the CI system. https://github.com/semantic-release/semantic-release — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[vmx]

Something less automatic than Semantic Release would be Standard Version. From what I can tell it does almost exactly what aegir release is currently doing.

[achingbrain]

I've used semantic release on previous projects, it works well.