Release cycle
We are following Semantic Versioning for our latest releases. Currently, we are before stable release so we may introduce breaking changes in minor version updates because we are still gathering feedback and improving the product.
Release cycle
We don't have scheduled releases. The releases done as we ship new features or bug fixes.
Channels
| Channel | Description | Versioning | Published after |
|---|---|---|---|
latest | Main release channel | x.y.z | testing in nightly |
nightly | Testing and feedback gathering | x.y.z-{hash} | change was merged to main branch |
Fixes
We are shipping fixes as soon as they are ready. Fixes are release first on the nightly channel and then promoted to the latest channel.
Right now we don't do patching of outdated versions. We recommend using the latest version.
Deprication Policy
Stable
For stable tools and features, we will follow our deprecation policy. We will announce the deprecation in advance on our blog and mark it in documentation as well.
Beta
All tools, features, and APIs that are marked as beta are subject to change.
We will try to keep the changes to a minimum, but we won't guarantee that we will follow our stable deprecation policy.