Release Notes
What changed, what broke, and what to do about it. Read this before upgrading a production deployment.
Entries below describe the shape of a release note rather than a shipped history. Replace with real release content before publishing.
1.8
Added. Tool SDK support for Go and Rust, reaching parity with Python and TypeScript. Resumable uploads for files above 100 MB. Per-tool permissions for MCP servers, replacing the previous per-server grant.
Changed. The runtime now reports unready rather than failing requests while the database is unreachable, so load balancers drain it instead of returning errors.
Deprecated. Per-server MCP permission grants. They continue to work and will be
removed in 2.0; migrate with arble mcp permissions <name>.
1.7
Added. Memory encryption at rest with project-scoped keys. Workflow pause and
resume at step boundaries. arble server drain for graceful shutdown.
Fixed. Streaming runs no longer terminate when a client disconnects; the run continues server-side and must be cancelled explicitly.
Upgrading
Migrations are additive within a minor release, so the previous version keeps running against the new schema during a rollout. Run them as a discrete step before rolling the application:
arble server migrate
Test any upgrade against staging restored from a production backup. Migration duration scales with data volume, and that is not a number to discover in production.