Skip to content

Tale v0.5.77

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Oct 20:18
· 79 commits to main since this release
v0.5.77
b4931db
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

  • When an agent's workspace has reached its limit of four concurrent executions, a new run
    waits for a place instead of failing. Finishing a run wakes the oldest waiter in that
    workspace; waiting does not consume an automatic retry.
    Task automation
    · #4481
  • Coding agents can discover their granted workspace tools even when they call
    workspace_status through the workspace_tool wrapper. The bridge routes that exact
    discovery call to the existing status endpoint. Tool permissions and session authentication
    still apply; an agent does not gain a tool by discovering it.
    #4496
  • An agent that implemented a task cannot delegate the review of its own result, even if it has
    the review-delegation permission. An independent manager can still hand the captured review
    to an eligible reviewer through the existing guarded workflow.
    Review delegation
    · #4487
  • Message information shows the model and provider used for a reply, token usage and timing,
    and the serving provider, region or specific model version when that information is available.
    An unreported region stays Not reported rather than being inferred from a provider's name.
    Reply details
    · #4493
  • Operators can collect a fresh managed-deployment acceptance receipt with tale deploy accept.
    It checks the completed deployment, running images and migration ledgers, and verifies that
    the canonical HTTPS origin reaches the frontend and API processes observed locally. A
    different installation running the same version is refused.
    CLI install
    · #4492
    · #4497
  • German and French interface wording follows the existing product labels more consistently,
    including Arbeitsbereich, Inhaber and Conservation légale. The German website's
    navigation, page eyebrows and product demos use Agenten and Richtlinien; some page titles
    and text still say Agents and Governance
    (#4483). Stored settings and translation keys
    are unchanged.
    #4489
    · #4490

Upgrade notes

  • Back up the application and knowledge databases, configuration, keys and external stores
    before deploying. Relative to v0.5.76, this release adds no database migration, operator
    environment variable or Compose service. When upgrading from an earlier version, retain the
    v0.5.76 upgrade requirements,
    including the ordered knowledge-corpus migrations and the prior-release requirements linked
    there.
  • Deploy the matching platform, sandbox spawner and sandbox-runtime images to receive the
    workspace-capacity and tool-discovery repairs. The platform, web, docs, UI docs, AI gateway and
    sandbox images now run Bun 1.4.2 instead of 1.3.12, and the sandbox runtime's bun is pinned to
    1.4.2 as well. The runtime upgrade uses a full deployment; a configuration-only update cannot
    install these changes. Existing tool and secret grants are preserved.
    #4486
  • Use this release's CLI and compatible runtime for deployment acceptance. Prepare the bundle
    with its full deployment source reference and complete the normal deployment first. Older
    bundles remain deployable, but cannot provide the new acceptance proof without the
    source-derived migration inventory and compatible serving processes. Acceptance requires
    the bundle, full CLI and deployment source commits, and the independently selected version
    without the v prefix. It observes state at that time; it does not promise that routing or
    processes remain unchanged later.
  • Acceptance does not apply configuration, restart services or run migrations. It takes the
    deployment lock and creates and removes a private temporary bundle copy. Docker and HTTPS
    observations share a 120-second budget. Preparation elapsed time counts toward that budget,
    but filesystem copy and cleanup cannot be interrupted by it. Use an external process
    supervisor when a whole-command deadline is required. The public serving-process identities
    are correlation data, not credentials. They arrive in a new Tale-Serving-Identity response
    header on Tale's health endpoints, including the frontend's /api/health and the API's
    /api/health/ready, so a proxy in front of Tale must pass it through; the JSON bodies are
    unchanged.
    Acceptance requirements
  • The release candidate source contract (.github/release-candidate-contract.json) adds backend
    integration's Verify current deployment acceptance ledgers step. An adopter that pins the
    contract's digest must review the new digest before adopting this release.
    #4492
  • If you grant task_delegate_review, deploy this release first: v0.5.76 accepts a delegation
    from the implementation agent of the reviewed work.
    #4487
  • Known issues carried into this release include the projects overview's older Environment
    wording (#4454). For replies that call tools,
    the timing breakdown can include tool execution within model phases; do not treat those
    phases or output speed as isolated model benchmarks.
    #4498

API contract changes

None in this range. The contract stays at 3.17.0: 141 operations.

What's Changed

Full Changelog: v0.5.76...v0.5.77

Contributors

yannickmonney
Assets 8
Loading