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.

7 posts tagged with "Deprecation"

View All Tags

Deprecation of MongoDB 3.4 support

Retool is phasing out support for MongoDB Server version 3.4 and earlier. Organizations with an unsupported version of MongoDB Server connected to Retool must upgrade to MongoDB Server 3.6 or later.

  • For cloud organizations, support for MongoDB Server 3.4 and earlier has already been removed.
  • For self-hosted organizations, support for MongoDB Server 3.4 and earlier will be deprecated in the Q2 2026 stable release. It will be removed in the Q3 2026 stable release.

MongoDB Server 3.4 has been end of life (EOL) since January 2020. We recommend upgrading to a currently supported MongoDB release.

Python 3.10 end of life

Python 3.10 will reach end of life on October 31, 2026. After this date, Retool will no longer support Python 3.10 in Workflows.

What's changing

New and existing workflows on Python 3.10 will continue to run but they will not be supported. They will not be automatically migrated to a newer version.

How to upgrade existing workflows

Python 3.14 is rolling out to cloud instances and will be available in an upcoming self-hosted release.

  1. Open the workflow and go to the Languages & Libraries tab.
  2. Click ... next to Python and select Update version.
  3. Choose Python 3.14 and click Apply.

When you upgrade, Retool automatically identifies built-in libraries your workflow uses and installs them as custom libraries. Python 3.14 is mostly backwards-compatible, but Retool recommends publishing a workflow release before upgrading so you can revert if needed.

See Configure Python version for full details on how to upgrade and revert to a previously published release.

Timeline

DateEvent
April 2026Python 3.14 available
October 31, 2026Python 3.10 End-of-Life (EOL); support removed from Retool Workflows

Deprecation of Databricks connector version 1.0

Retool has deprecated version 1.0 of the Databricks connector. If your organization has any Databricks resources that still use this connector version, update the resource configuration to use the version 2.0 connector.

Self-hosted customers must also enable the Java DBConnector to use version 2.0 of Databricks connector.

Change the connector version from the Databricks resource's configuration settings. Any existing queries that previously worked with version 1.0 will continue to work with version 2.0.

The option to use version 1.0 of the Databricks connector will be removed in Q2 2025 from cloud instances and subsequent releases for self-hosted instances.

Deprecation of MySQL Connector version 1.0

Retool has deprecated version 1.0 of the MySQL connector. If your organization has any MySQL resources that still use this connector version, update their configuration to use the version 2.0 connector.

The option to use version 1.0 of the MySQL connector will be removed in Q2 2025 from cloud instances and subsequent releases of self-hosted Retool.

Removal of image download functionality for external app users

These features are no longer available on cloud instances and self-hosted instances on version 3.114 or later.

Due to potential security concerns, Retool is removing certain functionality that enables external app users to download images. No security breach or active vulnerability has occurred, and you do not need to take any security-specific actions.

External and embedded, publicly available apps will no longer support:

  • Download Image columns in the Legacy Table component. Use an alternative method, such as a Link or Button column type, for image URL links. Retool strongly recommends you migrate to the current Table component instead.
  • Export PDFs with images hosted on separate domains. All other components will be included in the PDF export. Retool recommends moving your publicly-hosted images to be hosted on the same domain as your Retool instance. For example, you could use images that are natively uploaded to the Image component, stored in Retool Storage, stored in Retool Database, Base64-encoded, or stored in an Amazon S3 bucket.