[unRekable]

What changed and why

The community Discord's #releases channel was set up to receive every release automatically; the wiring was missing. When a release is published, the publish job now posts one line to the channel: the version and the download address, with the note that checksums sit in SHA256SUMS on the release page.

How it activates

The webhook's URL lives in the repository secret DISCORD_WEBHOOK_URL (an admin sets it to the #releases channel's webhook URL). While that secret is unset the step skips itself, so this change is safe to merge before that; and continue-on-error keeps a Discord hiccup from failing a published release.

Nothing references the URL itself anywhere in the repository, only the secret's name.

For the other channel

#github (pushes, pull requests, issues) is better served by a repository webhook pointing at that channel's webhook URL, which is an admin's two minutes in Settings, Webhooks. Deliberately no webhook for #contributions: that one is a conversation channel, the feed lives in #github.

Test

The step runs only on GitHub's runners (this workflow triggers on v* tags and manual dispatch, so pull requests do not execute it). The jq -n --arg payload construction is the standard form and jq is preinstalled on ubuntu-latest; the YAML was checked by hand and the step skips on every run until the secret exists.