Define version policy and set pipeline to use it #29

New issue

Open

opened 2026-08-22 01:48:35 +00:00 by zaprit · 1 comment

zaprit commented

2026-08-22 01:48:35 +00:00

Owner

Currently the package versions are all over the place, we should clean up the security.md for this as well.
Releases should be as follows:
Stable releases - Tagged releases that have been thoroughly tested
Pre-releases - Tagged releases that need to be tested
Nightly builds - Purely package builds that are built from main

These should be available as "streams" for the auto-updater/update server.

Currently the package versions are all over the place, we should clean up the security.md for this as well. Releases should be as follows: Stable releases - Tagged releases that have been thoroughly tested Pre-releases - Tagged releases that need to be tested Nightly builds - Purely package builds that are built from main These should be available as "streams" for the auto-updater/update server.

zaprit added this to the 2.0 milestone

2026-08-22 01:48:35 +00:00

zaprit added the

documentation

enhancement

labels

2026-08-22 01:48:35 +00:00

zaprit self-assigned this

2026-08-22 01:48:35 +00:00

zaprit added this to the 2.0 project

2026-08-22 01:48:35 +00:00

zaprit commented