Self-hosted Retool Edge release 3.240
Release notes for the Self-hosted Retool 3.240 edge release.
Releases on the Edge channel occur weekly. Each release occurs one week after the equivalent release for cloud-hosted Retool.
Edge releases are available for organizations that want the latest features or to use closed beta functionality. Retool recommends most organizations use Stable releases unless you have a specific need for Edge releases and can keep your deployment up-to-date.
Retool supports only the most recent release on the Edge channel. As Edge releases are weekly, bug fixes and improvements are included in the next release. All previous releases are then considered deprecated.
Self-hosted Retool 3.240
No longer supported
Edge release notes
Bug fixes, improvements, and other incremental updates across all edge releases in this release.
| Type | Description |
|---|---|
| 3.240.011 changes↑ | |
| added | Added support for Gemini 2.5 Flash stable model. [#63016] |
| added | Added streaming support for the self-hosted managed key proxy. [#63003] |
| added | Added support for AWS Secrets Manager integration to use EKS Pod Identity Associations for authentication. [#62969] |
| added | Added Retool AI to role permissions. [#62928] |
| fixed | Fixed an issue where moment.tz.names() and other static method access of sub-namespace function objects in moment were not working correctly. [#63049] |
| fixed | Fixed an issue causing intermittent failure when protecting query library queries that use a resource with multiple environments. [#63064] |
| fixed | Fixed broken documentation links for resource types in queries. [#63121] |
| fixed | Fixed an issue causing an infinite toast loop when renaming a workflow. [#63078] |
| fixed | Fixed an issue where MongoDB resources could not override the default authMechanism. [#62978] |
| improved | Improved error messaging for invalid Retool Storage queries where there is a slash in the folder name. [#63037] |
| changed | Changed MySQL resources to use the improved MySQL Connector by default. Changed Databricks resources to consistently use the Java DB connector for better performance and reliability. V1 Connectors for MySQL and Databricks are deprecated and cannot be used anymore. [#62865] |
| 11 changes | |