forgejo/.forgejo
Earl Warren 6e94be527a
chore(ci): remove old releases from forgejo-integration
The releases are created when:

* a tag is pushed to the integration repository it will create a
  vX.Y.Z release
* a new commit is pushed to a branch and mirrored to the integration
  repository, it will create a vX.Y-test release named after the branch

When both vX.Y.Z and vX.Y-test release are present, the end-to-end
tests will use vX.Y.Z because it comes first in release sort
order. This ensures that a last round of end-to-end tests is run from
the release built in the integration repository, exactly as it will be
published and signed.

In between stable releases, the vX.Y-test releases are built daily and
must be used instead for end-to-end testing so that problems can be
detected as soon as possible. For that to happen, the stable release
must be removed from the integration repository and this is done 24h
after they were published.

The vX.Y-test releases are removed if they have not been updated in 18
months. As of August 2024 it is possible for a LTS to still be needed
in tests over a year after it was last updated, although it is
unlikely that such a lack of activity happens, there is no reason to
remove the test release before that.
2024-08-10 15:16:00 +02:00
..
issue_template docs: add a PR checklist template (#4564) 2024-07-22 05:23:54 +00:00
testdata/build-release chore(ci): do not hardcode go version, use go.mod instead 2024-08-03 11:53:55 +02:00
workflows chore(ci): remove old releases from forgejo-integration 2024-08-10 15:16:00 +02:00
cascading-pr-end-to-end chore(ci): optimize end-to-end runs 2024-08-08 17:53:12 +02:00
cascading-release-end-to-end chore(ci): optimize end-to-end runs 2024-08-08 17:53:12 +02:00
pull_request_template.md docs: add a PR checklist template (#4564) 2024-07-22 05:23:54 +00:00