Updates, changes, and improvements at Retool.
Refer to the stable and edge release notes for detailed information about self-hosted releases.
You can now test deployments when using Source Control, preventing changes that leave your Retool instance in a broken state. Retool added the Test source control changes endpoint to the Retool API, which enables you to test whether implementing a change will result in deployment issues.
You can also incorporate this check into your continuous integration process if desired.
Enterprise users can now protect organization-level themes using Source Control. This enables you to safely replicate organization-level theme configurations across multiple instances of Retool. You can use protected themes with any of Retool's supported source control management (SCM) providers.
Branching is not supported for themes. You can merge changes into the remote repository, but you can't create a branch for themes using Source Control.
Retool will deprecate the use of YAML for protected apps, queries, and resources in Source Control. Support will be removed in self-hosted Retool 3.196 and later.
Self-hosted organizations still using YAML serialization of these elements in Source Control must migrate to Toolscript prior to upgrading.
Organizations with self-hosted deployments must manually deploy latest changes when upgrading to self-hosted Retool 3.52 or later to ensure that recent updates to Source Control are applied.
You can now enable collaborators on Source Control branches. Source Control branches are private by default and only allow changes by the owner. On collaborative branches, multiple users can commit changes and submit pull requests to protected elements.