Release channels

The SDKs ship on two channels from the same source. Which one you are on is decided by how you install, and you stay on it until you change that.

Stable

What every ordinary install resolves to. Breaking changes land here only on a major version, and the documentation at the site root describes this channel.

Pre-release

The next SDK line, published to the same registries and downloadable by anyone — but never the default. A pre-release is what you install when you want to try the next line early, or when you are running the local evaluation bundle, whose SDKs are cut from it.

Nobody lands on it by accident. pip skips pre-releases unless you pass --pre or pin the exact version, cargo will not resolve one for an ordinary version requirement, and on npm the pre-release sits under the next dist-tag while latest stays on the last stable release.

Pin the exact version if you want a pre-release to stay put:

pip install 'mubit-sdk==0.14.0rc1'
npm install @mubit-ai/sdk@0.14.0-rc.1
cargo add mubit-sdk@0.14.0-rc.1

Moving between them

The wire contract is the same on both channels, so a pre-release client talks to a stable instance and the other way round. Moving back is a plain install of the stable version — there is no migration step and nothing is written to your instance in a pre-release-only format.

The migration guide covers what changed in the pre-release line, and versioning covers the compatibility rules.