debian-forge/.github/workflows
Simon Steinbeiss b1d703a260 Enable scheduled upstream releases
Instead of a human pushing a tag with the release notes let a bot do the
work.
The bot is part of our composite action in osbuild/release-action on the
create-tag branch. It calculates the next subsequent release version and
creates a tag based on pull request titles associated with the changes
since the last release.
Finally the tag is pushed to the repository.

Unfortunately GH Actions don't allow for reliably fortnightly schedules,
so we do an additional check that determines if this is an even or an
odd week. This will help with correctly scheduling alternating osbuild
and osbuild-composer releases.

For reference, we do exactly the same for osbuild-composer already:
https://github.com/osbuild/osbuild-composer/blob/main/.github/workflows/create-tag.yml
2022-03-24 00:04:49 +01:00
..
checks.yml Update to the latest osbuild-ci container (with skopeo) 2022-02-10 14:43:17 +01:00
coverity.yml ci: schedule coverity only for osbuild/osbuild 2020-07-07 08:26:53 +02:00
create-tag.yml Enable scheduled upstream releases 2022-03-24 00:04:49 +01:00
release.yml release-action: Send notification to our Slack channel 2021-12-11 14:06:13 +01:00
tests.yml ci: add test_executable to test matrix 2022-02-15 13:25:23 +00:00
trigger-gitlab.yml trigger-gitlab: do not interpret the fetch_pulls outputs 2021-10-21 11:35:08 +02:00