I agree with what the answer @Gypsy and to complement, any problem that exists even in the repository and that is corrected later should be released in a new update so that the flow of a software update is correctly followed, imagine that someone has already downloaded the version 1.0.0
or 1.1.0
, then probably if you could edit some of it this would cause inconsistency for those already using the specific version.
Think that each problem fix is already an update, so even minor problems should also be part of the x.x.x
(x.x.x.x
), even if the problem is in a repository file.
According to the http://semver.org/lang/pt-BR/, given a version number MAJOR.MINOR.PATCH
(x.x.x
), increment the:
- Larger version (
MAJOR
): when making incompatible changes to the API.
- Minor version (
MINOR
): when adding functionality while maintaining compatibility.
- Fix version (
PATCH
): when fix faults maintaining compatibility.
In case your problem is PATCH
, then if the problem was in 1.0.0
and in 1.1.0
you should create a new tag 1.1.1
.
This explanation in the end made me correct the versioning of a repository of mine. I was using so :
1.4
,1.6
,1.7
– Wallace Maxters