Exclusive version updates about keel

[rusenask]

Hi, currently this approach would only work for patch releases. I guess it would be good to understand your versioning - major version informs about backwards incompatible changes, introduced to the public API, right?

Maybe we could use build metadata for this (http://semver.org/):

Build metadata MAY be denoted by appending a plus sign and a series of dot separated identifiers immediately following the patch or pre-release version. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Identifiers MUST NOT be empty. Build metadata SHOULD be ignored when determining version precedence. Thus two versions that differ only in the build metadata, have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, 1.0.0-beta+exp.sha.5114f85.

Or it could be additional annotation/label. But it does sound a bit redundant since all patch versions should be okay in minor version policy.

Have you considered having separate docker images from dev/staging/prod environments?

[stevenbarragan]

Yeah, it feels that I'm trying to bend semver rules. I need to rethink my workflow.

Thank you.