Skip to main content

Changelog

Updates, changes, and improvements at Retool.

Refer to the stable and edge release notes for detailed information about self-hosted releases.

Retool removed versions 1.0 and 2.0 of the Microsoft SQL integration. The removal is live on cloud instances. It reaches self-hosted instances in Retool 4.88 Edge and the first release of the next stable cut.

Apps, workflows, and queries that depend on Microsoft SQL resources still using version 1.0 or 2.0 stop working. This follows the deprecation announced in July.

What to do​

Update each affected resource to version 3.0:

  1. Open the resource from the Resources page.
  2. Change Connector version to Version 3.0.
  3. Save your changes.

Version 3.0 accepts array values in query parameters, so you don't need to rewrite existing queries. If you haven't intentionally created a resource on an older integration version, your resource is likely already on version 3.0.

You can now use the Build with tests setting to validate that your app is functioning as expected and catch unintended changes before you publish your app to end users. Toggle this setting on from the chat settings or from the debug console.

note

App testing is currently rolling out to cloud organizations. It is not yet available to self-hosted organizations.

When app testing is enabled, the agent writes or updates tests whenever it adds or changes behavior in your app. By default, the agent writes a small set of behavioral tests. After the agent makes any changes to your app, Retool runs the tests related to those changes. If any of them fail, Retool sends the failures to the agent, which continues working to fix them.

Retool is now available on Google Cloud Marketplace. Work with your Retool account team to set up a private offer. After you accept it in your Google Cloud console, Retool is billed through your Google Cloud account. To learn more, read the announcement blog post.

The Retool Blueprints listing enables you to deploy self-hosted Retool to Google Kubernetes Engine (GKE) as a prepackaged Kubernetes app. Deploying Blueprints requires a Retool license key. Blueprints has no usage fee, but Google Cloud charges for the GKE resources you run.

Retool now supports the use of private npm registries for apps. Enterprise organization admins can add registries in Settings > App Security, and builders can then ask the agent to install packages from them. Use private registries to:

  • Download a specific package from a private registry. For example, pull a design system that you host on your own servers into your apps.
  • Download all packages from a specific registry. Add a registry as the default, or route entire npm scopes (such as @acme) to it. Registries can require authentication with a bearer token or basic auth, or allow anonymous access.
  • Control which packages are allowed. Build your own registry with rules about what it permits users to download. For example, enforce a minimum package age that you configure yourself.

Private registries must be npm-compatible and use HTTPS.

Admins on Enterprise plans can now set spend limits on AI usage using the new Spend Controls tab in the AI monitoring settings. On self-hosted instances, this page is named AI visibility.

Limits work for both Retool-managed keys (credits) and bring your own key (tokens). Set an organization-wide default user limit, then override it for specific users or groups. You can also set a limit on a model to cap its total usage across your organization. For each, you can set a Notify at limit, which sends notifications and lets usage continue, and a Block at limit, which blocks further usage. A user's effective limit is their own limit, then the highest limit among their groups, then the default. Model limits apply separately from user and group limits.

The Spend Controls tab in AI monitoring settings, showing the Users table with Notify at and Block at limits.
The Spend Controls tab in AI monitoring settings, showing the Users table with Notify at and Block at limits.

When a builder reaches a block limit, AI app building pauses and they can send a limit increase request to admins. Admins can review requests in the Spend Controls tab or from the Action center on the Overview page, then approve a higher limit or deny the request. Retool also sends email notifications when limits are reached.