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.

44 posts tagged with "Self-hosted"

View All Tags

Self-hosted Retool 3.284 Stable

Self-hosted Retool 3.284 is now available on the Stable release channel. Retool encourages prompt upgrades to each Stable version once it is released to ensure that your deployment stays secure and up-to-date.

This release is off-cycle, and it is intended to bring Assist to self-hosted organizations that prefer to use the Stable channel. The next Stable release will occur at the end of Q4 2025, and Stable releases will continue quarterly thereafter.

Retool supports each Stable release for six months. During this time, Retool will release patch updates that contain bug fixes or security updates. Patch updates do not contain functionality changes and can be applied more quickly than performing a full version upgrade.

After six months, a Stable release is considered deprecated. You can continue using a deprecated release but it will no longer receive updates. At this time, you should upgrade to the latest Stable release.

Retool provides versioned product documentation for supported Stable releases. When browsing Retool Docs, use the version dropdown menu in the navbar to switch to a relevant version.

Result sync in Invoke Agent block

To enable Result (sync) for Agents in self-hosted Retool version 3.284.0 or 3.284.1, reach out to your account manager.

In version 3.284.2, Result (sync) for Agents is available by default, and admins can disable it in Settings > Beta by toggling the Agent blocks in workflows sync mode feature flag.

You can now see the output of an agent run with the Result (sync) return type when using the Invoke Agent block in workflows.

  • The Result (sync) type is the default setting. This returns the direct result of the agent's output.
  • The Run state (async) type returns the agentRunId, agentId, and status only. It does not include the output of the agent.

Self-hosted Retool 3.253 Stable

Self-hosted Retool 3.253.0 is now available on the Stable release channel.

Retool releases a version on the Stable channel every 13 weeks (quarterly). A Stable release is generally four versions behind the cloud-hosted version at the time.

Preparation and testing of a Stable version occurs approximately four weeks prior to its release. Stable releases are rigorously tested before they are published. As the release cycle is less frequent, administrators can more easily maintain and upgrade deployments.

Retool supports each Stable release for six months. During this time, Retool will release patch updates that contain bug fixes or security updates. Patch updates do not contain functionality changes and can be applied more quickly than performing a full version upgrade.

Retool provides versioned product documentation for supported Stable releases. When browsing Retool Docs, use the version dropdown menu in the navbar to switch to a relevant version.

After six months, a Stable release is considered deprecated. You can continue using a deprecated release but it will no longer receive updates. At this time, you should upgrade to the latest Stable release.

Removal of unsupported JDBC connectors

Retool removed some JDBC connectors that were inadvertently included in certain self-hosted release versions. These include:

  • Actian Ingres/Vector JDBC Driver.
  • Clickhouse JDBC Driver.
  • IBM Data Server Driver for JDBC.
  • IBM Informix JDBC Driver.
  • Trino JDBC driver.

These JDBC connectors are not supported by Retool for self-hosted deployments. If you have created a JDBC resource using these connectors, update its configuration as needed to make use of your own preferred JDBC drivers.

Retool has since released patch updates for affected releases that remove these connectors.

Code executor changes in self-hosted 3.251 and later

Self-hosted Retool 3.251 and later contain two notable changes to the code-executor service:

  • A container running code-executor is required to run workflows and custom API authentication. Previously, these features could be run in a sandbox in the backend container. Retool's security team has become aware of a sandbox escape and will no longer be supporting sandboxing in the backend. For more information refer to the disclosure page.
  • Traffic to the private 192.168.0.0/16 IP address range is blocked by default. If you want to disable this security configuration, follow the instructions in the code-executor security privileges documentation.

Removed Self-hosted preview of Retool Agents

Retool removed the preview release of Agents for self-hosted organizations since Agents is now in public beta with the 3.234.0 edge release and it will be available in 3.253 stable. This preview release was intended for deployment into a non-production environment, and was created as a mechanism to allow Self-hosted organizations the opportunity to create agents prior to their availability in an edge or stable release.

Self-hosted preview of Retool Agents

A preview release of Retool Agents is currently available to self-hosted organizations for deployment into a non-production environment. This preview release is intended to allow customers to preview and create proof-of-concepts that show how agents may work in their environment.

As Retool is continuously working to develop and improve Retool Agents to meet the high standards required for production environments, this preview release is not intended for production use and this build should not be deployed in an existing Retool installation or deployment. Retool recommends that self-hosted organizations create a new deployment in a private network alongside resources to which you intend to connect. Retool reserves the right to make changes to the agents preview without notification.