Release notes
Touba 1.4.0
The language, runtime and JavaScript and Python SDKs use version 1.4.0. The matching VS Code extension is 1.0.6.
Packages and approvals
The application retains minimum approval requirements for imported tools. A package update that changes its governance contract requires explicit review. Accepting the package preserves the application's requirements and the permissions granted by the host.
Traces connect calls to package versions and digests, the admitted lock and the approval request. They also retain a pseudonymous signer reference and the attested role.
Preparation and confinement
- A fresh project with packages and fragments needs one
write, followed bycheck. - Fragment changes appear in the plan. Their comparison digests are retained
in
touba.project.jsonand belong in version control. touba sdk sandbox pythonprepares a Python handler inventory for review. macOS and Linux preserve its virtual environment and explicitly granted access. Python shared libraries on Linux are included in the inventory.- SDKs retain precise integrity and admission diagnostics.
Handler confinement is enabled explicitly through sandbox.required.
The Windows backend remains planned for a later release.
Getting started
The documentation provides a guided path. AIR-reading errors explain how to check the compiled file and selected project. Once compilation finishes, saved changes are visible to subsequent commands and Explorer.
Migrate from 1.3.1
Keep your data and handle suspended operations with their original build. Update the CLI, then each project's SDKs:
touba update
touba sdk install javascript
touba sdk install python --manager uv
touba prepare --mode plan
touba prepare --mode write
touba prepare --mode check
Install only the SDKs used by your application. Review and commit
package_contracts, tool_policies and fragment_baselines in the project
configuration. If an older fragment already differs, follow the
documented reconciliation.
Regenerate confinement inventories on each machine and rerun business tests.
Payment validation and uniqueness rules remain the business service's responsibility.
Touba 1.3.1
This update brings together the features and fixes since Touba 1.1.0. The runtime and JavaScript and Python SDKs share version 1.3.1; the matching VS Code extension is 1.0.5.
Approval and governance
- A tool can require approval of its exact arguments, with a required role, deadline and separation of signers. The requirement also applies through imports, skills and agent-selected calls.
- A protected call consumes one tool-budget unit across an approval pause and resume.
- Handlers receive the run, caller and active-agent provenance.
See Operation approval and business uniqueness.
Applications and SDKs
- Prepared resources reach executions and remain available after a resume, with fingerprint and permission checks.
- Both SDKs can create and resume explicit compensation.
- Hosts can activate declared triggers and lower their limits.
- Diagnostics distinguish a refused entry (
ProjectEntrypointNotAllowed) from a busy effect journal (EffectJournalBusy).
Updating from 1.1.0
Back up projects and finish or reconcile suspended executions using their original build. Update the CLI, then each project's required SDKs:
touba update
touba sdk install javascript
touba sdk install python --manager uv
touba prepare --mode write
Update SDKs alongside the runtime: older closed schemas can reject the new
execution_context provenance field. Unknown manifest and host-configuration
fields are now reported; correct them before preparation. Newly protected tools
require runtime 1.3.1.
For older JSON journals, follow the explicit SQLite migration. Retain the original journals and their associated checkpoints. Then rerun your application's business tests. Vendor, amount and cross-run invoice uniqueness checks remain in the business service.
Touba 1.1.0
This version adds verified distribution updates:
touba update --check
touba update
touba update --rollback
Explorer improves resource and budget details. Resume checks reject altered checkpoints, changed host contracts and consumed approvals. SDK diagnostics retain structured causes.
Before migrating, back up data and complete or reconcile pending operations. Install the distribution, then update each project's SDK. Restoring an earlier executable keeps the current business data. Follow the update guide for the full procedure.
Later release notes will appear here after qualification and distribution.