When a project already has a release, each new version goes out from Draft a new release on the project page. The form starts with your files, because the file name usually says the version already — so you no longer type a number the file would have filled in for you.

The order on the form

1. Main installer — the file people get from the Download button.
2. Additional files, if you have them — builds for other platforms, a checksums file, a source archive. The list under the boxes shows what each file will become.
3. …or external download URL, if the file is hosted somewhere else.
4. Version / tag — by now it already says what it will be, for example Will be 2.3.0, read from mytool-2.3.0.exe.
5. Release notes (summary) and What's Changed (one item per line).

Project details stay folded underneath; open them only if something about the project itself changed. Then press Publish release.

The version box

• Leave it empty and the number read from your file is used; with no number in the name, it continues on from your last release. Type one and yours wins.
• Under the box, Latest release: shows the version already out, so you can see what comes next.
• If the file name says a version that is already published, a warning appears straight away, before anything is uploaded: rename the file or type a new version.

Good to know

• The fields, their names and the rules are the same as before; only the order changed.
• If a submit is refused — a taken version, a file type the site does not accept — the form comes back with your text kept, and a note right above the file boxes asks you to pick your files again. Browsers cannot keep picked files after a failed submit.

More on releases: how the version number is chosen, your first release, dropping files on the form and taking a picked file out. More guides at https://jmtechpower.com/articles.