Upgrades and versions

Kaveon does not yet publish a stable compatibility or support window. Pin deployments to immutable revisions and test metadata changes before production rollout.

The root package/API version and Rust crate versions are not yet a coordinated semantic-version compatibility contract. There is no documented downgrade mechanism.

Upgrade procedure

Read release notes and compare configuration.
Back up metadata and retain current images/binaries.
Test against a non-production metadata copy and representative sources.
Run relevant platform and Engine checks.
Deploy compatible API and Studio revisions, then verify auth, SQL Lab, DLM, and dashboards.
If migrations are incompatible, roll back application artifacts and restore metadata together.

Release channels

dev is the integration branch. Engine CI may replace the moving engine-dev prerelease. Until stable policy exists, use a commit SHA or immutable image digest instead of latest.