forgejo/.forgejo/workflows
Earl Warren 9e662fe2cd
[RELEASE] publish container images tagged with the major version
Now that semantic versions are used, the major version must be used
instead of major.minor to distinguish releases with breaking changes.

Before:

Forgejo v1.21.1-0, tags 1.21.1-0 and 1.21
Forgejo v1.21.2-0, tags 1.21.2-0 and 1.21
Forgejo v1.22.1-0, tags 1.22.1-0 and 1.22

After

Forgejo v7.0.0 tags 7.0.0 and 7
Forgejo v7.0.1 tags 7.0.1 and 7
Forgejo v7.1.2 tags 7.1.2 and 7
Forgejo v8.0.1 tags 8.0.1 and 8
2024-03-02 19:48:28 +08:00
..
build-release-integration.yml [CI] name the test release after the latest v*-dev tag 2024-02-23 15:37:46 +01:00
build-release.yml [CI] name the test release after the latest v*-dev tag 2024-02-23 15:37:46 +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 [RELEASE] publish container images tagged with the major version 2024-03-02 19:48:28 +08:00
testing.yml [CI] run frontend checks 2024-02-25 23:08:09 +01:00