TestCafe versioning
TestCafe uses Semantic Versioning for its versions. Release cycle must strictly follow rules and conventions of SemVer, however there are still some nuances that should be noted.
-
Major releases: Version upgrades from
0.#x.#y
to0.#x+1.0
. Might contain breaking API changes and significant new features. -
Minor releases: Version upgrades from
0.#x.#y
to0.#x.#y+1
. Must contain only bug fixes, compatibility patches and insignificant backward-compatible features.
-
Beta builds: Version format
0.#x.#y-beta.#z
. In a nutshell they are nightly builds, published versions of code from themaster
branch.#z
is incremented for each new alpha build with the same#x
and#y
, and set to0
when#x
or#y
changes. Might contain bugs and compatibility issues, and are published only for testing purposes. -
Release Candidate builds: Version format
0.#x.#y-rc.#z
. These build are intended to be used for testing before releasing of a new stable build. They should be mostly stable, however some bugs can be found in them, and can be used for preparing for an upgrade to a next stable build, or trying out new features.#z
is incremented for each new RC build with the same#x
and#y
, and gets zeroed when#x
or#y
changes.