Every release of your project has a version, like 1.4.0. On Draft a new release the Version / tag box is optional — here is how the version is chosen when you publish.

The order: you, then the file name, then the next number

1. What you type always wins. Type 2.0.0-beta or 2026.1 and that is the version.
2. Left empty, it is read from your file name — the main installer first, then your additional files. It needs at least two numbers with a dot between them; a v in front is fine.
3. No version in any file name? It continues on from your latest release by adding one to the last number.

Before you publish, the grey text inside the empty box shows the version you will get.

Examples from file names

• mytool-2.4.0-setup.exe → 2.4.0
• photo_resizer_v3.1_win64.zip → 3.1
• kettle-2.0.0-arm64.AppImage → 2.0.0
• tool-7-setup.exe → no version (a single number is not enough), so the next number is used

Examples of the next number

• latest 1.2.3 → 1.2.4
• latest 2.0 → 2.1
• latest 1.0.9 → 1.0.10

The very first release of a project with no version anywhere is 1.0.0.

A version can only be used once

If the version — typed or read from the file name — is one your project already has, the form stops before anything is uploaded and says: Version 1.4.0 is already published for this project. Use a new version number. Pick a new number, or rename the file if the version came from its name. The "next number" never lands on a taken one: it skips numbers an older release already uses.

More on publishing: Publish your software in one step and Got a project but no download yet?. More guides at https://jmtechpower.com/articles.