You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, stable 1.3.0 is considered an "update" when the user has manually opted into pre-release 1.4.0-pre1.
It's a combination of the way SMM checks for updates and semver
When it checks for updates it sets all profile versions to *, which only matches releases
But when selecting a prerelease and checking "or newer" (i.e. >=x.y.z-pre.a), that would match only newer releases and same version prereleases, but SMM's update check has to set the range to *, otherwise it would never offer an update if the user selected a fixed version