Earl Warren 014e533206 [RELEASE] decouple the release name from the version number ... The release name, as provided by FORGEJO_RELEASE, is used to build OCI images and binary files. Although it can be the same as the Forgejo version, it is not a requirement. When the FORGEJO_RELEASE environment variable is set, use it as a default for naming the binary file instead of FORGEJO_VERSION. For instance, when building from the forgejo branch here is what is desired: FORGEJO_VERSION=7.0.0-g2343 GITEA_VERSION=1.22.0 VERSION=vforgejo-test The name of the release is also displayed with forgejo --version for sanity check purposes. Before: FORGEJO_VERSION is the computed version GITEA_VERSION is set manually VERSION defaults to FORGEJO_VERSION forgejo --help does not display VERSION After: FORGEJO_VERSION is the computed version GITEA_VERSION is set manually RELEASE_VERSION defaults to FORGEJO_VERSION VERSION defaults to RELEASE_VERSION forgejo --help displays VERSION		2024-02-17 15:27:35 +01:00
..
build-release-integration.yml	[RELEASE] build test releases	2024-02-17 11:52:50 +01:00
build-release.yml	[RELEASE] decouple the release name from the version number	2024-02-17 15:27:35 +01:00
cascade-setup-end-to-end.yml	[CI] cascade end-to-end must not try to merge feature branches	2024-02-10 10:53:04 +01:00
e2e.yml	[CI] Forgejo Actions e2e tests (squash) generate	2024-02-05 13:33:59 +01:00
mirror.yml	[CI] mirror to forgejo-integration daily instead of each commit	2024-02-17 11:55:52 +01:00
publish-release.yml	[CI] pin go 1.21	2024-02-07 12:19:56 +01:00
testing.yml	remove debug print	2024-02-09 11:27:58 +01:00