What's New
Releasify now disallows non-Semver versions
While using non-Semver versions in your NuGet package was always incorrect and resulted in undefined behavior, due to #868, these are now a full non-starter. We now require packages to have Semver-compatible versions names. Note that this doesn't affect your EXE versions, which can still use all four Win32 version numbers.
Bug Fixes
- Allow uppercase characters in SemVer versions (#924, thanks @runehalfdan)
- Sign DLL and .node files during Releasify
- Ensure that Stub Executables pass along their parameters to the target