b1d703a260
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 |
||
|---|---|---|
| .. | ||
| workflows | ||
| codecov.yml | ||
| mergify.yml | ||