[Bug] Use standard versioning (3.1.0) instead of "3.1.0-stable" to fix persistent Winget update prompts #444
Description
The Problem:
Nora currently uses the versioning format x.y.z-stable (e.g., 3.1.0-stable). While this is clear to humans, it breaks Semantic Versioning (SemVer) logic used by package managers like winget, Scoop, and Chocolatey.
In SemVer, any version with a hyphen and a suffix is treated as a pre-release. Therefore, winget treats 3.1.0-stable as being "older" or "lesser" than 3.1.0.
Current User Experience:
-
User installs Nora via winget.
-
The winget repository (manifest) lists the version as 3.1.0.
-
The app reports itself to the registry as 3.1.0-stable.
-
Winget sees these as mismatched strings.
-
Every time winget upgrade is run, it tells the user Nora has an update available, even if they just installed it.
The Comparison Logic:
| Installed Version | Available in Repo | Winget Status |
|---|---|---|
| 3.1.0-stable | 3.1.0 | |
| 3.1.0 | 3.1.0 | ✅ Up to date |
Suggested Change:
For stable releases, please use the standard MAJOR.MINOR.PATCH format (e.g., 3.1.0).
- If you want to denote stability, the absence of a suffix (like -beta or -rc) is the standard way to signal a stable release in the software industry.
Environment Info
-
Nora Version: 3.1.0-stable
-
Package Manager: winget (Microsoft.AppInstaller) v1.11.510
-
OS: Windows 10/11
Supporting Screenshot
