ci: create the GitHub release with the App token so dc.yml fires - #1102
Conversation
Events produced by the default GITHUB_TOKEN never trigger other workflows, so the rmk-v0.9.0 release created by publish.sh did not fire dc.yml's Discord announcement. Mint the release App's token (the same one release-pr.yml uses) and hand it to publish.sh as GH_TOKEN.
Deploying rmk-rs with
|
| Latest commit: |
7c11546
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://fdf373b2.rmk-4a2.pages.dev |
| Branch Preview URL: | https://fix-publish-release-token.rmk-4a2.pages.dev |
Remove comments explaining the use of the release App's token.
Size Report
|
The rmk-v0.9.0 GitHub release was created by publish.sh with the workflow's default
GITHUB_TOKEN, and events from that token never trigger other workflows — so dc.yml'srelease: publishedDiscord announcement did not fire (its last run is still v0.8.2).Mint a token from the release App (same secrets release-pr.yml already uses) and pass it to publish.sh as
GH_TOKEN, sogh release createproduces an event that triggers dc.yml. Tag pushes still use the checkout credentials and are unaffected.