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.

Enterprise organizations can now implement multi-instance releases for apps using any supported SCM provider: AWS CodeCommit, Azure Repos, BitBucket, GitHub, and GitLab.

To enable multi-instance releases, navigate to Settings > Source control > Edit settings and turn on Enable multi-instance releases.

This feature enables you to publish different release versions across instances, making it possible to test a newer version on staging or development instances before promoting to production. Get started with multi-instance releases for apps.

Organizations on paid plans can prompt the app building agent to use resource environments in published apps. Resource environments enable you to run a function against different configurations of the same resource, such as staging and production, and were previously only available in Edit mode for apps.

note

Published apps do not include an environment toggle by default.

Optionally, prompt the agent to add a UI element that allows app users to switch between resource environments.

When the user is not in the Finance Admin group, use the staging resource environment.
I want to use this app across resource environments. Add a dropdown in the top right corner.

In addition, you can use the _environment URL query parameter to open an app in a different environment, such as ?_environment=staging. This URL parameter works automatically and does not require prompting.

Organizations on the Business plan now have access to Retool-provided AI models for app building. These models, prefixed with Retool, have been tuned by Retool for enhanced performance and speed for app building.

The following Retool-provided models are supported:

  • Retool Mini
  • Retool Power