Retool's Slack integration now supports the files.getUploadURLExternal and files.completeUploadExternal APIs for uploading files. Slack ended support for their files.upload API on March 11, 2025, and this endpoint is no longer available in the Retool Slack integration.

For most users, no action is required to access the new APIs. For self-hosted organizations that set the SERVE_LOCAL_SPECS environment variable, you must upgrade to version 3.168.0-edge, patch release 3.148.2, or patch release 3.114.17 to access this change.

The workaround described in the Action Required: Update Slack queries using files.upload changelog entry is no longer required.

Slack is ending support for their files.upload API on March 11, 2025. Refer to the Slack changelog for more information.

Retool is working to update our Slack integration as quickly as possible. In the meantime, if you need files.upload functionality, you can use a REST Query to utilize the new files.getUploadURLExternal and files.completeUploadExternal APIs.

This workaround is temporary, and Retool will restore access to file upload functionality within the Slack integration as soon as possible. Another changelog post will be made when the ability to upload files is restored. Other functionality in the Slack integration remains uninterrupted.

Self-hosted Retool 3.148 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 3.114 is now available on the Stable release channel.

As a result of new features an improvements in self-hosted Retool 3.114, base memory usage for this and future releases is approximately 20% higher. If you experience performance issues after upgrading, consider increasing the allocated memory for your deployment.

Retool Storage is now available to self-hosted organizations as a file management interface for an S3 or Google Cloud Storage bucket. Because you control your own file storage bucket on self-hosted deployments, there are no data limits or overages for Retool Storage on self-hosted deployments.

Retool will deprecate the use of YAML for protected apps, queries, and resources in Source Control. Support will be removed in the Q2 2025 stable release of Self-hosted Retool.

Self-hosted organizations still using YAML serialization of these elements in Source Control must migrate to Toolscript prior to upgrading.

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

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