Skip to content

Tale v0.5.76

Choose a tag to compare

View all tags
@github-actions github-actions released this 07 Oct 12:58
· 207 commits to main since this release
v0.5.76
26765dc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

  • Website scans skip rendering a page only when its plain HTML carried all of the text the browser
    showed at the page's last render. In v0.5.75, nine tenths of the text was enough, so a change
    drawn only by the page's JavaScript could go unnoticed. Pages whose plain HTML falls short are
    rendered on every scan. This was a known issue in v0.5.75.
    Crawling
    · #4451
  • A comment you are editing in a task discussion keeps its editor and draft when new comments push
    the discussion past 100 rows, whether or not the editor has focus. An open delete confirmation
    or actor preview stays open the same way. This was a known issue in v0.5.75.
    #4460
  • Keyboard focus can now move into a task's agent preview and reach View more. Escape closes
    the preview and returns focus to where it opened. This was a known issue in v0.5.75.
    #4457
  • If the code for the embedding alert, the New project dialog or the document preview fails to
    load, for example while offline, the dashboard stays in place. The alert is left out, the
    New project dialog closes, and the document preview says "The document preview could not be
    loaded. Try again." with a Try again button, instead of replacing the chat transcript. This
    was a known issue in v0.5.75.
    #4458
  • When a task holds more than 64 deliverables, a deliverable replaced under the same name now
    counts as the newest, so the next run stages it. Deliverables written before this release keep
    their earlier order until they are written again. This was a known issue in v0.5.75.
    #4452
  • Resumed task runs receive the current task description, including an explicit notice when it
    has been cleared. Their prompt reflects edits made since the earlier run instead of relying
    only on the description retained in the conversation.
    #4479
  • A project agent explicitly granted task_delegate_review can hand a pending native agent review
    to another independent agent in the same project. The handoff checks the captured approval,
    source run and evidence revision, preserves the task's status, implementation assignment and
    future reviewer settings, and starts no run. The recipient needs task_review and its own
    eligible review run to decide the review.
    Task automation
    · #4482
  • Usage charts add up the selected days, weeks or months in the database, so a large
    organization's 90-day view no longer reaches the 20,000-row read limit early and shows partial
    totals. The current and previous periods stay separate even when they share a week or month.
    This was a known issue in v0.5.75.
    #4474
  • Governance's Model access and Default models editors show their scope, role and mode
    options, such as Team, Admin or Allowlist, in the session's language; German and French
    sessions saw them in English before. Budgets also translates role options and table targets.
    Stored rules are unchanged.
    #4462
    · #4478
  • When an immediate Model access save fails, the editor restores the previous controls,
    including after confirming a change that affects default models. Fresh saved configuration
    updates the open editor and closes edit or delete dialogs whose selected rule may have changed.
    A later failed save preserves an earlier successful save while the cached policy is unchanged.
    #4266
  • The agent details panel uses the names shown elsewhere in the interface: Connectors and
    Plattform-Tools in German, and Skills and Connectors in French, where "Compétences"
    is the name of a different Governance feature.
    #4461
  • Runtime selectors and related guides consistently use Agent runtime in English,
    Agent-Laufzeit in German and Environnement d'agent in French. Saved runtime values,
    API fields and documentation URLs are unchanged.
    #4480
  • The website's German and French pages use the app's names for Knowledge and Automations
    (Wissen and Automatisierungen, Connaissances and Automatisations) and correct several German
    product terms.
    #4472
  • Screen readers no longer announce the language, website, Shopify and Enter-key icons on their
    own; an icon is announced only when it is given a name. The contacts table's language column has
    a header that screen readers announce as "Language", and the composer's send hint is read as
    "Enter to send".
    #4468
  • Math rendering uses KaTeX 0.18.2, which fixes GHSA-238p-pmpm-9mq7 (CVE-2026-103923, low
    severity): earlier versions could treat properties inherited from an already polluted
    Object.prototype, such as trust, as renderer options. KaTeX 0.18 prefixes its internal CSS
    class names; Tale's own styles don't use them.
    #4422
  • A project's Environment tab says that its credentials are stored for the project and aren't
    passed to agent runs yet, and points to the agent's Secrets grants instead. Its editor applies
    the server's rule for names (an uppercase letter first, then uppercase letters, digits or
    underscores, at most 64 characters) and explains an invalid name in the session's language. The
    projects overview documents the tab in English, German and French, including who can manage the
    credentials and how to replace or remove a value.
    Project credentials
    · #4469
    · #4463
  • The CLI reference documents tale deploy --bundle <directory> --configuration-only. It applies
    only managed instructions, agent tool grants and automations to the healthy runtime of an
    already-ready deployment, without a pre-deploy snapshot or restart; use it when only those
    change and runtime and identity inputs stay the same. The new agent-tools resource updates
    an existing agent's tool set while preserving its model, instructions and secret grants.
    German and French guides also correct interface labels, including provider, storage and
    approval controls.
    CLI install
    · #4470
    · #4464
    · #4477
    · #4482
  • The guides describe the Password change required screen. Members see it at sign-in after an
    administrator sets or resets their password, or when it expires under the organization's
    rotation policy, and set a new password before continuing; an administrator's reset also signs
    the member out of all sessions.
    When a password change is required
    · #4465

Upgrade notes

  • Back up the application and knowledge databases, configuration, keys and external stores
    before deploying. On startup, the knowledge database container (knowledge-db in Compose)
    applies the knowledge-corpus migration 00000000000014_website_url_strict_change_check.sql from
    this release's db image to tale_knowledge. It adds nullable etag_v2, last_modified_v2
    and probe_hash_v2 columns to public_web.website_urls, clears the change checks that earlier
    releases stored once, and adds a trigger that discards any check written to the earlier columns.
    The previous platform keeps working on the migrated database during a rolling deploy, but its
    scans render every page, because its checks are discarded. Upgrade the knowledge database
    container to this release's db image and wait for its migrations to finish before starting the
    new platform images. Keep the columns and the trigger during a rollback: the migration has no
    down step. The first scan of each website after the upgrade renders every HTML page again; later
    scans skip unchanged pages as described above.
    Upgrade and recover
    · #4451
  • If upgrading directly from v0.5.74 or earlier, also apply the
    v0.5.75 upgrade notes;
    these steps remain required even if you skip running v0.5.75. Upgrade knowledge-db to the
    v0.5.76 release db image and wait for knowledge-corpus migrations
    00000000000013_website_url_change_check.sql and
    00000000000014_website_url_strict_change_check.sql to complete, in that order, before starting
    the new platform images. The backend applies 0153_two_factor_first_required_sign_in.sql on
    startup; it is forward-only, so retain its column during an image rollback. Update any pinned
    SANDBOX_RUNTIME_IMAGE to the matching v0.5.76 runtime image, which includes the sharp security
    update. Use the release's Tale CLI when updating retained 0.5 Compose runtimes so it can adopt
    the static-assets named volume; existing data volumes and host mounts must still match the
    managed topology.
  • Relative to v0.5.75, this release adds no application database migration, environment variable,
    or Compose service; knowledge-corpus migration 14 remains required as described above.
    To adopt agent-tools or captured review delegation, first deploy this release's runtime and
    use its matching Tale CLI. Older runtimes refuse the new capability. Grants are explicit:
    an agent-tools resource replaces the complete tool set, so include every grant to retain;
    [] clears it. Review the native plan and read back the applied tools. This release does not
    automatically grant review or delegation authority, change secret grants, or route pending
    reviews. Runtime upgrades still use a full deployment; configuration-only applies to later
    changes against that ready compatible runtime.
    CLI install
    · #4482
  • Known issues in this release:
    • The projects overview still describes the Environment editor's earlier name check and the
      tab's earlier wording about task runtimes. Where they differ, the tab and its editor are
      current.
      #4454

API contract changes

The contract moved from 3.16.0 to 3.17.0 (141 → 141 operations). Read the API reference's versioning section before upgrading a pinned client.

Added operations: none.

Removed operations: none.

Changelog

3.17.0 — 2026-10-07: the project-agent tools vocabulary gains task_delegate_review, an explicit grant to transfer a pending native agent review with exact source and evidence preconditions. Native task_get includes its bounded delegation receipt for reconciliation. Tale CLI can manage an agent's tools through a conditional tools-only configuration facet; saved models, instructions and secret grants remain independent. No public REST delegation or agent-verdict endpoint is added. Additive.

What's Changed

Full Changelog: v0.5.75...v0.5.76

Contributors

renovate and yannickmonney
Assets 8
Loading