As we're rolling out more and more Retools and iterating on them alongside making changes to our APIs, we're starting to feel the necessity of ensuring that versions stay in sync between a given Retool and the APIs that it queries. We embed Retools in the same codebase as the API, and thus we could accomplish this if we could "pin" the Retool version via its URL in our code config, therefore not having to manually time our API deploy with hitting "Publish" on a new version immediately.
Out of curiosity, have you received this feature request before? Does it seems like an expensive feature to build, hosting multiple live versions of Retools simultaneously?
Guessing without any knowledge of Retool internals, it sounds like one way this might be achievable on the backend might be to enable multiple historical versions to be active rather than just 1, and having some sort of queryparam to specify which version (defaulting to the latest of the active versions).