When releases are published, we don't need to add releaseVersion=latest to the url, end users always see the latest release. In the topic you linked, the issue was that the release was published before the last changes were made. We must publish a release after any changes. Editing the app on a version that has been published does not add changes to the existing version, a new one has to be created.
Thanks for your response. Let me clarify - the end user experience is working fine, but we are wondering whether there is a way for user acceptance testers to easily pin themselves to the latest version for testing purposes before the UI gets in front of end users? It would be great if different environments could be set to different release versions, for example.
Thanks for expanding on your use case! This is possible with Source Control, which is available on the Enterprise plan. You can book a demo to see if the additional features from this plan are what your organization needs.