Rules for increasing the patch number in semver

According to semver

"PATCH when you make backward compatibility bug fixes.

and

"Error correction is defined as an internal change that corrects incorrect behavior."

With this in mind, we can say that I have a variable that can be called, for example, color. And for some reason I need to change the color value.

v1.0.0
$color: #FFF;

v1.0.1
$color: #F0F0F0;

Now this is a variable that is defined in the API as what users can call. I did not change the actual variable that is being called, but only the return value. To do this, I have to make changes to my code, to the API element, and I have to merge this code into a production branch. But does something like this really guarantee an increase in the patch version number of your API?

+3
source share
1 answer

The semantic version point is for managing software system dependencies. Semantic versioning provides an organized specification to standardize this process to reliably monitor the state of these systems. As stated in the specification,

, . .

api ( ) , . . , ; .


, , . , , , , $color api , v1.0.0.

, , . :

  • , , .
  • , , (. 9 10 ).

. .

TL; DR

, v1.0.0 , v1.0.0 . , , . , X.Y.Z.

+2

All Articles