Ever since Release 0.8, KBCLI and KubeBlocks have their own release pace. And usually it is infeasible to set such a constraint that KBCLI and KubeBlocks shoud have exactly the same pre-release version.
Instead we can raise the constraint and check if the two have the same minor version.
KBCLI and KubeBlocks adopts semiversion, which encodes a version by a three-part version number Major.Minor.Patch.
E.g. KBCLI 0.9.x should works for KubeBlocks of version 0.9.y. where 0 is the major version, 9 is the minor version, and x and y indicate patch number. In the above figure, we should not raise the warning.
Ever since Release 0.8, KBCLI and KubeBlocks have their own release pace. And usually it is infeasible to set such a constraint that KBCLI and KubeBlocks shoud have exactly the same pre-release version.
Instead we can raise the constraint and check if the two have the same minor version.
KBCLI and KubeBlocks adopts semiversion, which encodes a version by a three-part version number
Major.Minor.Patch.E.g. KBCLI 0.9.x should works for KubeBlocks of version 0.9.y. where
0is the major version,9is the minor version, andxandyindicate patch number. In the above figure, we should not raise the warning.