Paulo thanks!
For anyone else, what Paulo says is correct but my additional tip is to assume that publishing releases is based on current changes and not the release changes. For example, I am working on version 1.0 and I have "published it". I created a new version 1.1 and I created it directly after publishing v1.0. However, this is not the expected behavior as v1.1 will only have the code relevant to v1.0. In order to make updates, you must wait until you made code changes and then release v1.1.
In other words:
Create new app > publish v1.0 > make changes > publish v1.1 > make changes publish v1.2.
Any changes you make will not reflect to Retool users until you publish the changes to a new version. Hope that clears any confusion!