Post silent changelog to Discord on release#493
Merged
Conversation
Adds a step to release.yml that posts each new release's auto-generated notes to the project Discord's #changelog channel via a channel-scoped webhook (secret DISCORD_CHANGELOG_WEBHOOK). The post is silent: flags:4096 (Discord's SUPPRESS_NOTIFICATIONS / @silent) means the message lands in the channel and marks it unread but triggers no push/desktop notification for anyone, independent of per-channel settings. No @everyone/@here is ever included, and allowed_mentions.parse:[] is belt-and-suspenders against any @mention in the notes pinging. The step skips cleanly when the secret is unset, so releases never break. In-line in release.yml rather than a release:published-triggered workflow because the GITHUB_TOKEN-created release won't fire downstream workflows (GitHub anti-loop safeguard) — same reason bump-and-release dispatches release.yml explicitly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Adds a step to
release.ymlthat posts each new release's auto-generated notes to the project Discord's #changelog channel via a channel-scoped webhook.Behavior
flags: 4096is Discord'sSUPPRESS_NOTIFICATIONS(the@silentmechanism) — the message lands in the channel and marks it unread, but triggers no push/desktop notification for anyone, independent of each member's per-channel notification settings.@everyone/@hereis ever included;allowed_mentions.parse: []is belt-and-suspenders against any@mentionin the generated notes pinging.DISCORD_CHANGELOG_WEBHOOKis unset, so releases never break.Why in-line in release.yml
A
release: published-triggered workflow would never fire — the release is created byGITHUB_TOKEN, and GitHub's anti-loop safeguard blocks token-created events from triggering downstream workflows (the same reasonbump-and-release.ymldispatchesrelease.ymlexplicitly).Required to activate
Repo secret
DISCORD_CHANGELOG_WEBHOOKset to the channel webhook URL. Until then the step no-ops.🤖 Generated with Claude Code