Cut new release?

[Brantone]

Hey,
Originally I was curious about cutting a new release for all the changes (if they're all completed), but then I also noticed that "latest" is still showing as 0.9.5 (https://github.com/marcells/node-build-monitor/releases) , whereas code is already up to 0.9.8 (and I assume latest changes will bump that up).
T�hanks in advance.

[marcells]

Currently, there is not automated version incremented or release on Github created. But you're right, I have to implement that.

The docker containers are always updated automatically, if that helps you for now.

[marcells]

I only updated the version number, when something in the frontend changes. Cause then the web frontend reloads automatically, after the service is updated and restarted.

[Brantone]

Initially, I was thinking less of an "automated version increment" and more just generic release of features (front or back end) and bumping https://github.com/marcells/node-build-monitor/blob/master/package.json#L3 based on something like http://semver.org

[marcells]

Now I easily can bump a version with grunt bump. This will also create a new tag/release automatically. In addition for each tag a separate docker image is built. So, if there are any issues with a new version, you can revert it easily.

[Brantone]

Awesomeness! 👍