Skip to content

v0.1.37

Latest

Choose a tag to compare

@github-actions github-actions released this 16 Aug 23:34
· 12 commits to main since this release

Tura 0.1.37

Released on 2026-08-17. Changes are relative to
v0.1.36.

Highlights

  • Fixed npm-installed Tura resolving its project root from the slim tura-ai
    wrapper package. The wrapper now points TURA_PROJECT_ROOT at the native
    platform package's target/release directory, where the packaged agents,
    personas, provider catalog, prompts, commands, and tool schemas live.
  • Kept persistent state independent from versioned node_modules directories:
    the wrapper preserves an explicit TURA_HOME but no longer invents one under
    the npm package, so upgrades do not replace sessions or lock files.
  • Added fail-fast validation for missing packaged runtime resources before the
    native CLI starts, with an actionable reinstall error.
  • Strengthened release verification to parse every packaged JSON configuration,
    load every built-in agent and persona through the installed CLI, and verify
    that all packaged tool manifests are discovered and enabled. Each agent's
    configured capabilities must resolve to an exposed tool.
  • Extended the manual Linux, macOS, and Windows npm 12 workflows to test both
    global and local installs of the published version in addition to simulated
    tarball installs. macOS continues to test Node.js 24.18.0; Linux and Windows
    use Node.js 22.22.2, all with npm 12.0.2.

Upgrade notes

  • Upgrade a global installation with npm install --global tura-ai@0.1.37.
  • For a project-local installation, run npm install tura-ai@0.1.37 and then
    npx --no-install tura.
  • If Windows reports EPERM while replacing tura_gateway.exe, close any
    running Tura CLI, TUI, GUI, or gateway process and retry the install.
  • No session database migration is required.
  • The main package and all four native platform packages must use version
    0.1.37.

Validation

  • Release builds install the generated main and platform tarballs without npm
    lifecycle scripts, run tura --help, and then start the packaged gateway to
    validate all agents, personas, provider configuration, commands, schemas, and
    exposed tools.
  • The three opt-in OS installation workflows repeat the checks against the
    published tura-ai@0.1.37 package with npm 12 for global and local installs.

Links