fix: check for semantic version

[ShGKme]

• Fix: Stub Executable fails when passing 4-level version string #131

StubExecutable expects app's version to be a valid semantic version

• See: https://github.com/bitdisaster/Squirrel.Msi/blob/master/src/StubExecutable/Semver200_parser.cpp

However, electron-wix-msi successfully creates a package with an invalid semantic version, e.g., Windows version 1.2.3.4. The created packages then cannot be launched from the created shortcut or Stub Executable.

This PR adds a check for version to be a valid semantic version and to prevent successful creation of an invalid package.

To make the change less destructive, it tries to transform a Windows version into a semantic one in the most probable case: 1.2.3.4 -> 1.2.3+4

[MLDMoritz]

This works for me. Please merge @felixrieseberg - Ty!

[MLDMoritz]

Did some testing. On initial installation this seems to work fine, when updating to another version, it wont.

E.g. fromn 1.2.3+1 to 1.2.3+2 the stub won't launch, even when built with @ShGKme changes.

[ShGKme]

I'll have a look at update

[MLDMoritz]

Just sharing my thoughts...

We build for Intune, with version of 1.2.3+300 this would lead to an msi version of 1.2.3.300 which would upload fine to intune.

If we update with version 1.2.3+301 this would work fine for intune, because its using 1.2.3.301. However, as the StubExecutable parses 1.2.3+301 I think it cannot find the newest version anymore, as it's correctly ignoring the metadata. It's not been validated, but I guess this is what happens.

I think this would be an issue within Squirrel.Msi ?

[MLDMoritz]

@ShGKme I created a fork of your patch at https://github.com/MLDMoritz/electron-wix-msi/tree/fix/semantic-version with the new StubExecutable from https://github.com/MLDMoritz/Squirrel.Msi

When multiple versions with the same major.minor.patch but different build numbers (e.g., 1.2.3+4 and 1.2.3+5) are installed, ensure the stub executable launches the correct version by comparing build metadata numbers.

This fix enhances FindLatestAppDir() to:

• Identify versions with identical major.minor.patch numbers
• Extract and numerically compare their build metadata
• Select the version with the highest build number

Resolves issue where stub can't distinguish between versions that differ only by build number.