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.
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.
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.
- Download the target distribution and verify its digest.
- Install it using the instructions for your system.
- Update the affected projects’ SDKs and run their tests.
touba update --json
touba sdk install javascript
touba sdk install python
touba update provides update information; installation remains an explicit
action. Choose the SDK your project uses, or both if your application requires them.
For a project with suspended approvals or processing, read Change builds without losing pending work before replacing the installation. Backups and the original build support a recovery process consistent with the project’s state.
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.