#

Format: MAJOR.MINOR.PATCH[-prerelease] (Semantic Versioning 2.0.0)

Bump THIS by editing the version line below; CMake reads it and propagates

the number everywhere (the app's runtime version, the About screen, and the

Windows .exe resource). Lines starting with '#' and blank lines are ignored;

the first remaining line is the version.

#

How to bump (see notes/reference/versioning.md for the full guide):

- PATCH (0.8.3 -> 0.8.4 -> ... -> 0.8.47): THE DEFAULT. Almost every change is a

PATCH – fixes AND ordinary features. The PATCH number is NOT capped at 9; let it

climb into 2-3 digits. Favor this.

- MINOR (0.8.x -> 0.9.0): RARE – only a genuine milestone (a big, headline feature

set). Don't roll a new MINOR just because something is "a feature"; prefer PATCH

and, when unsure, flag it rather than auto-bump. (Project leader's call on feel.)

- MAJOR (0.x -> 1.0.0): the first real release / a stability promise.

- prerelease label: -alpha (early), -beta (feature-stable), -rc.1 (release

candidate). Drop the label entirely for a final release. Pre-1.0 (0.x)

already signals "in development, things still move."

#

WHO bumps what (kept current by default): the AI assistant keeps this line

current – it decides and applies MINOR and PATCH bumps in the same commit as

the change that warrants one. MAJOR (-> 1.0.0) is reserved for the project

leaders (Twilight) and is NEVER bumped automatically. App fixes -> PATCH,

features -> MINOR; docs/notes/test/CI-only commits do not move the number.

#

Build identity (the git commit) is appended automatically by the build as

SemVer build metadata, e.g. 0.7.0-alpha+g1a2b3c4d – you do NOT edit that here.

0.14.2-alpha