Repository navigation
Tags
Tags
fix: MSIX version revision must be 0 — use Major.Minor.{build}.0 format
Microsoft Store rejects packages where the 4th version component
(revision) is non-zero. v0.3.7 incorrectly placed version_code as
the 4th component (1.6.1.97), causing the error:
'Apps are not allowed to have a Version with a revision number
other than zero specified in the app manifest.'
Fix: place version_code in the 3rd (Build) component, always use
0 for the 4th (Revision): Major.Minor.{version_code}.0
Example: version 1.6.1, CI run #99 → MSIX 1.6.99.0
fix: Windows MSIX version 4th component now uses build_number/GITHUB_… …RUN_NUMBER Previously the appxmanifest Version was always set to X.Y.Z.0 because the 4th component was hardcoded to '.0'. This caused Microsoft Store to reject new submissions with 'duplicate package identity' errors when the semver hadn't changed but the CI build number had incremented. Fix: use version_code (populated from build_number in jffi.toml, or auto-overridden by GITHUB_RUN_NUMBER in CI) as the 4th MSIX version component. CI run #78 with version 1.6.1 will now produce 1.6.1.78. Other platforms were unaffected: - Android: versionCode already used version_code correctly - iOS/macOS: CURRENT_PROJECT_VERSION already used version_code correctly Bumps jffi to v0.3.7
PreviousNext