Versions and Updates
Each Touba resource displays its own version in the Hub. The CLI, VS Code extension and packages can evolve at different rates.
During the language’s public validation, the main download offers the latest qualified build for your platform. Previous versions are retained to reproduce an installation and prepare a migration.
Touba 1.1.0
- Verified updates with
touba update, availability checks with--checkand restoration of the retained build with--rollback. - Explorer: improved resource details, budgets and navigation.
- Approvals: checkpoint integrity, host-contract binding and durable consumption checks reject altered or already consumed continuations.
- JavaScript and Python SDKs: aligned host contracts and diagnostics.
From 1.0.0, install 1.1.0 once from Downloads. Later updates can use
touba update. Back up project state and handle pending work before changing
builds. Update project SDKs separately.
Extension 1.0.2 accompanies this release, bringing Explorer to VS Code and matching bundled components. Its version remains independent of the language.
Identify your installation
touba version
The command shows the installed version and build. In VS Code, Touba: Check CLI identifies the loaded extension and selected CLI.
| Element | What its identity describes |
|---|---|
| Touba version | Shared distribution of the language, compiler, runtime and CLI |
| Build | Exact source state and built contents |
| VS Code extension | Extension version and compatibility of its bundled components |
| Package | Package version and Touba requirements declared in its manifest |
| Documentation | Edition corresponding to the version being read |
| AIR, traces and manifests | Data formats, separate from the software version |
The website’s version does not determine your installed version. Compare the
build reported by touba version with the one listed for your platform in the
Hub. Your local installation is updated separately.
Download and verify
The Hub lists files for your system with their version and SHA-256 digest. SHA256SUMS and CHECKSUMS.json also support verification of the complete set. Follow the installation guide to compare the downloaded file’s digest.
A published version retains its contents. A correction ships under a new version, with its change notes.
Choose the documentation
The public edition selector displays exact version numbers. Choose the edition for your installation to find the relevant syntax, commands and contracts.
Each edition’s examples are checked against its distribution. Editorial updates clarify that edition; new features belong to their own version’s documentation.
Prepare an update
Read the change notes, particularly changes to syntax, persisted formats, execution controls and SDKs.
- Stop affected services and back up their data.
- Follow the update instructions for your installed build.
- Check the new installation with
touba versionandtouba doctor. - Update the affected projects' SDKs, then run their tests.
touba sdk install javascript
touba sdk install python
Choose the SDK your project uses, or both if the application requires them. Updating the CLI does not automatically replace project SDKs.
For suspended work, read Change builds without losing pending work before updating. Restoring an earlier CLI does not restore business data: keep the corresponding project backup.
Previous versions
Published versions remain identifiable so installations can be reproduced and migrated. A withdrawn version is marked in its catalog with the reason and recommended replacement.