Skip to content

Tale v0.5.89

Choose a tag to compare

@github-actions github-actions released this 13 Oct 13:09

Highlights

  • Native deployment provisioning now accepts the Better Auth 1.7 built-in password capability. Upgrading a host that already runs v0.5.87 or v0.5.88 completes the break-glass administrator reconciliation instead of stopping after the service containers become healthy.

Upgrade notes

  • From v0.5.88 to v0.5.89 no database migration or manual configuration change is needed. The release is a deployment hotfix for the native CLI; rerun the normal Tale CLI deployment/adoption flow after the images and CLI are published.
  • The native CLI still refuses a disabled or malformed password policy and verifies the declared credential hash before completing provisioning.

API contract changes

The contract moved from 3.43.0 to 3.44.0 (161 → 161 operations). Read the API reference's versioning section before upgrading a pinned client.

Added operations: none.

Removed operations: none.

Changelog

3.44.0 — 2026-10-13: coding agents may sign in to the MCP endpoint unless the operator turns it off (TALE_MCP_CLIENT_METADATA_DOCUMENTS and TALE_MCP_DYNAMIC_CLIENT_REGISTRATION now default to on): the discovery documents answer on a default deployment — the endpoint's protected-resource metadata at /.well-known/oauth-protected-resource, and the sign-in server's own with the agent scopes, refresh_token, the metadata-document flag and, for a client that registers itself, a registration_endpoint — and the 401 of /api/v1/mcp carries the challenge 3.43.0 describes. agentOAuth joins the security schemes (OAuth 2.1 authorization code with PKCE, the seven scopes) and the endpoint's security lists it beside the API key. No operation, schema or API key behaviour changes.

What's Changed

Full Changelog: v0.5.88...v0.5.89