SatisfactoryModManager icon indicating copy to clipboard operation
SatisfactoryModManager copied to clipboard

Lower semver stable versions are considered valid updates to prereleases

Open budak7273 opened this issue 5 months ago • 0 comments

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

https://discord.com/channels/555424930502541343/1193986432574963782/1403246938639433799

budak7273 avatar Aug 08 '25 06:08 budak7273