Self-hosted Retool 3.33 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.

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.

Self-hosted Retool now includes default statement timeouts that apply when running upgrade migrations. If your organization has a self-hosted Retool deployment that uses PgBouncer with its main PostgreSQL database, you must update the PgBouncer configuration to ignore statement timeouts.

ignore_startup_parameters = statement_timeout

The new Linting and Performance tools, available within Debug Tools in the App IDE, provide additional methods for debugging and optimizing apps.

Linting​

Identify queries, code, and components that may affect app performance.

Performance​

View statistics related to app performance along with an overall performance score. This is a useful tool for measuring how changes affect an app's performance and provides guidance on how to optimize it further.

Configuring Resources in Retool can require handling sensitive values, e.g., database passwords or API keys. Starting in Self-hosted Retool 3.20 and later, you can store and retrieve secrets from Google Cloud Platform (GCP) Secrets Manager.

You can create custom URLs for web apps to make them more discoverable and easier to share with end users. With a custom URL set, end users can access apps at {domain}/app/{custom-url} or {domain}/p/{custom-url} if it's a public app.