2 Commits

Author	SHA1	Message	Date
Earl Warren	f250f89491	chore(ci): do not remove tags from forgejo-integration ... If the tag of a stable release is removed from integration, it won't be properly described when building the test release. It will be: 8.0.0-dev-1648-7b31a541c0+gitea-1.22.0 instead of: 8.0.1-5-7b31a541c0+gitea-1.22.0	2024-08-11 07:22:21 +02:00
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