Versioning and compatibility

Arcium publishes the CLI, Rust crates, TypeScript packages, and Arx node image as a coordinated release.

​

Choose an upgrade path

​

Understand compatibility

Starting with v0.11, releases are designed to preserve compatibility at the protocol and account level. Network upgrades should not invalidate existing MXEs, Clusters, or computation-definition accounts. Developer-facing APIs can still change. An upgrade might require source changes before you rebuild, even when deployed accounts remain compatible. The release notes identify required application and Node Operator actions for each release.

​

Update a project

Each component updates through a different mechanism:

1. Check the active CLI and Arcup versions:
   arcium --version
   arcup version
   
   Also check Arcium versions in your Cargo manifests, JavaScript package manifest, lockfiles, and Arx node image tag.
2. Read the release notes from your oldest component version through the latest release. Apply every required API or configuration change in order.
3. Update the components managed by Arcup:
   arcup self update
   arcup update
   
4. Set Arcium Rust crates and TypeScript packages to the same release. Follow the installation overview for current prerequisites. Node Operators should also follow Node setup for the current image and configuration.
5. Rebuild and test before deploying:
   arcium build
   cargo check --all
   arcium test