Skip to main content
Version: 1.3.1

Release notes

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.