Fix scheduled release CI trigger and add sparse release notes #754
+7
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempts to fix the issue where scheduled weekly releases don't trigger CI builds.
Problem
Release events created by workflows using
GITHUB_TOKENdon't trigger other workflows (GitHub Actions security policy to prevent recursive workflow triggering).Solution
GH_TOKENorGITHUB_TOKENin env--notes-start-tag- Generate sparse release notes comparing only against previous weekly tag (prevents pinging everyone with full history)--fail-on-no-commits- Prevent empty releases when no work has been done since last releaseChanges
.github/workflows/scheduled-releases.ymlenv: GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}block--notes-start-tag "$PREV_TAG"togh release createcommand--fail-on-no-commitsflagTesting
Can be tested via:
workflow_dispatchon Actions tabRelated
See also