Semantic versioning #683
davidfdezalcoba
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there! For the last versions, versioning changed from semantic versioning to a schema consisting of year.month.day of the release.
IMHO this is an inferior scheme, and I wanted to propose to go back to semantic versioning. Many of us have our homelabs automated, with renovate bot automatically updating versions for docker images and releases and gitops for automatic rollout.
A common scenario with renovate is to automatically merge (and thus deploy) minor and patch releases, which should contain no breaking changes. However, with the current scheme, there is no distinction, and any version could contain breaking changes. These last times I have found myself with a broken wizarr deployment because of breaking changes that should not have been merged automatically.
I currently see no downside in changing to semantic versioning, which is also quite standard in many other community projects. Please tell me so if there are many benefits I am not aware for this scheme!
Anyways, thank you so much for the effort in the wizarr development, awesome app!
Beta Was this translation helpful? Give feedback.
All reactions