Allowed Versions
You release Northstar Editor 3.2.0 after fixing a bug that caused projects to fail to save. You want users to move off 3.1.0. Add 3.2.0 to the app’s Allowed Versions list and remove 3.1.0 when you are ready to block it. A client on 3.1.0 then gets a UPDATE_REQUIRED response instead of a session.
Set the allowed list
- Open the app’s Settings → Allowed Versions page.
- Add each exact version string your app sends during initialization, such as
3.2.0. - Keep the list empty if you want every version to pass this check. Once you add entries, only listed versions are accepted.
- Test an allowed build and a build you intend to block before changing production access.
Before removing a version, publish a working update and tell affected customers where to get it. An app that receives UPDATE_REQUIRED should show an update message or link. It should not close without explanation.
How this differs from other release settings
- Allowed Versions decides whether the version currently running may connect.
- Release Channels decides which update link and release notes a signed-in identity receives.
- Hash Management checks a build hash. A version string is not a fingerprint of the executable.
For example, you can offer Beta 3.3.0-rc.1 to testers while both 3.2.0 and 3.3.0-rc.1 remain allowed. When you later remove 3.2.0, it is rejected even if the customer is still assigned to Stable.

