v0.50.0

What's new

• Tool response size limit. A tool call now stops reading an upstream response larger than 10 MB and returns a clear error (TOOL_RESPONSE_TOO_LARGE) that tells the model to narrow the request with filters, fewer fields or smaller pages. One huge response can no longer stall the server for everyone. Set TOOL_MAX_RESPONSE_BYTES to change the limit. This applies to the REST (including JSON-RPC and OData), GraphQL and SOAP engines, on Cloud and self-hosted alike. (#1279)

Changes

• Sentry SDK 11 and OpenTelemetry 3. @sentry/nestjs, @sentry/nextjs and @sentry/profiling-node move to 11.9, and the OpenTelemetry SDK to 0.300 / 3.0. Every data collection category of the new SDK (request bodies, headers, cookies, query strings, user, MCP tool arguments and results, AI content) is turned off explicitly, and streamed spans go through the same scrubber as events. Supersedes #1259 and #1260. (#1280)
• The minimum Node.js version for running from source is now 22.15 (required by OpenTelemetry 3). The Docker image is not affected.

Cloud

• The backend keeps about a week of logs (20 files of 100 MB). (#1278)
• Trust the missing intermediate certificate of warnung.bund.de, so the NINA connector works on Cloud again. (#1277)

Docs

• Prompts and FAQ for the Dolibarr (EN, FR), ERPNext, SQL Server and Oracle satellites. (#1276)

Full changelog: v0.49.0...v0.50.0