They both report to the system as the same application, just two versions of the 'same thing', therefore the system will always choose the newest version in any split-decision.
You can only change that before compile, i.e. at source.
You could try reporting it as a bug, get them to change the name the nightly reports to the system as - though don't hold your breath, this has always been the case for many apps with public betas.
From my own comments…
The issue is how the app iteself registers to the OS. If you check the data as to which app can open which file or resource, you find that though the OS will record all instances of all apps capable, it only has room for one default. After that it becomes a bit of an awkward dichotomy if you have 2 versions of the same app. It really wants to always open the newest version, but setting the pref to the release will hold it back to some extent.
Unfortunately, the versioning recognition doesn't work if one of the versions is already open - in that case it will always win the fight. This is simply not fixable at consumer-level, only before compile. The app must have a different signature to be recognised in that instance.
-no-remote
) to disable it, but I don’t know how to make this change permanent.