Greptile Summary

• Adds an optional DISCORD_RELEASES_ROLE_ID secret that, when set, prepends a Discord role mention (<@&ROLE_ID>) on its own line before the release announcement message.
• The implementation correctly uses ${DISCORD_RELEASES_ROLE_ID:-} to stay compatible with set -euo pipefail when the secret is absent, and delegates JSON-safe encoding to jq --arg mention.
• No changes to the Twitter/X announcement path; all additions are scoped to the announce-discord job.

Confidence Score: 5/5

Safe to merge — change is minimal, well-guarded, and handles the absent-secret case correctly.

No logic errors, security concerns, or breaking changes found. The role mention is optional, properly guarded with a -n check and ${VAR:-} expansion, and the newline-terminated mention is safely encoded through jq's --arg flag.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant GH as GitHub (release published)
    participant WF as release-announcements.yml
    participant DC as Discord Webhook

    GH->>WF: Trigger on release published
    WF->>WF: Check DISCORD_WEBHOOK_URL set?
    alt webhook not set
        WF-->>WF: Skip (exit 0)
    else webhook set
        WF->>WF: Check DISCORD_RELEASES_ROLE_ID set?
        alt role ID set
            WF->>WF: role_mention = "<@&ROLE_ID>\n"
        else not set
            WF->>WF: role_mention = ""
        end
        WF->>WF: Build payload via jq (mention + message body)
        WF->>DC: POST JSON payload
        DC-->>WF: 2xx OK
    end

_{Reviews (1): Last reviewed commit: "fix(release-announcements): include role..." | Re-trigger Greptile}

😤 @Devesh36 said "I will fix this" and then actually fixed it. Legendary behavior.

👋 Join us on Discord - OpenSRE : hang out, contribute, or hunt for features and issues. Everyone's welcome.