Earl Warren abf72a42e7 ci(release): upgrade v*.next.forgejo.org when the release is ready ... The https://v$major.next.forgejo.org instances are polling for new releases with a cron job every hour. This is not only a waste of resources because there is nothing most of the time, it also imposes a delay of maximum one hour when there is a new release. When the release is published, notify the corresponding instance that an upgrade is ready. In the request will 404 but leave a trace in the logs which can trigger an upgrade script if wakeup-on-logs is configured accordingly. GET https://v$major.next.forgejo.org/.well-known/wakeup-on-logs/forgejo-v$major * v8 - a daemon watching on the web server logs was installed for https://v8.next.forgejo.org and will perform the upgrade. * v7 - nothing will happen for https://v7.next.forgejo.org because it still relies on the hourly cron job. * v1.21 - nothing will happen because https://v1.next.forgejo.org does not exist. See also: * https://forgejo.org/docs/next/developer/infrastructure * https://code.forgejo.org/infrastructure/wakeup-on-logs		2024-07-01 12:52:59 +02:00
..
testdata/build-release	Update code.forgejo.org/oci/alpine Docker tag to v3.20	2024-05-25 02:05:40 +00:00
workflows	ci(release): upgrade v*.next.forgejo.org when the release is ready	2024-07-01 12:52:59 +02:00
cascading-pr-end-to-end	[CI] simplify end-to-end test cascading PR	2024-03-20 18:16:56 +01:00
cascading-release-end-to-end	[CI] simplify running end-to-end tests while building a release	2024-03-20 20:20:42 +01:00