We only use 2 points X.Y always unless there is really a patch which is extremely uncommon.
Developers choose the X and tooling chooses the Y. That is the developers only ever have to make a simple decision did I break it or not.
* these are still semver but just treat the patch as optional
* add tests for various combinations of updates
Previously, SemVer pre-release version was used to differentiate kind
of "branches", not allowing to cross pre-release on update.
According to SemVer spec, this should rather rely on the metadata.
New "keel.sh/matchPreRelease" annotation (or label) is added to disable
current keel behavior and consider the pre-release as a standard
SemVer versioning token.
For backward compatibility purpose, its value defaults to "true" if not
specified.
Closes#252
Also reviewed WatchRepositoryTagsJob tags handling.
Fixes#490
Michael McCallum
Aurélien Grenotton
Karolis Rusenas
Mate Ory