Add structured Discord webhook logging for release notifications

[juliusmarminge]

Summary

• Add structured logging around Discord release announcement dispatch, including startup, payload construction, request send, response receive, and completion.
• Log safe request metadata such as webhook origin, path shape, payload size, embed count, and mention usage to improve observability without dumping the full payload.
• Switch webhook status handling to inspect the actual response before raising an error, and add console pretty logging to the command runtime.

Testing

• Not run (not requested).
• Confirmed the command still builds the announcement payload and posts it through the webhook client path.
• Confirmed non-2xx Discord responses are now logged and converted into DiscordReleaseAnnouncementError.

---

Note

Medium Risk
Touches the release workflow and Discord webhook notification path; misconfiguration or stricter URL parsing could cause release announcements to fail (though continue-on-error mitigates workflow impact). Adds logging and changes HTTP status handling, which may alter error behavior on non-2xx responses.

Overview
Improves Discord release announcement observability by adding structured logs around command startup, payload construction, webhook request dispatch, and response handling in scripts/notify-discord-release.ts, without logging full secrets/payloads.

Tightens URL typing/validation by treating DISCORD_WEBHOOK_URL as a real URL config and parsing --release-url into a URL (and using .href when building embeds), and updates webhook posting to log/inspect the actual response status before converting non-2xx results into a DiscordReleaseAnnouncementError.

Updates the release workflow to source Discord role IDs from secrets (exposed as DISCORD_MENTION_ROLE_ID) instead of repo vars when invoking the announcement script, and enables pretty console logging via Logger.consolePretty().

^{Reviewed by Cursor Bugbot for commit 9a15254. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add structured logging and URL validation to Discord release webhook notifications

• Adds structured logging in postDiscordWebhook before and after dispatch, including webhook URL metadata and payload summary (embed count, mention syntax, content length).
• Changes releaseUrl and webhook URL types from string to URL, with --release-url now validated via Schema.URLFromString and DISCORD_WEBHOOK_URL validated via Config.url.
• Adds startup and completion logs to notifyDiscordReleaseCommand with annotations for target, role ID, release name, version, and tag.
• Switches Discord role ID env vars in the release workflow from vars to secrets.
• Enables Logger.consolePretty for human-readable output during command execution.
• Behavioral Change: non-2xx webhook responses now produce a DiscordReleaseAnnouncementError that includes the HTTP status code; invalid DISCORD_WEBHOOK_URL values will fail at configuration time.

^{Macroscope summarized 9a15254.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: e31638d9-b5c1-4163-8104-11fb766f5165

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch t3code/discord-webhook-logging

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[macroscopeapp]

Approvability

A prior Macroscope approval was dismissed. Re-evaluating 342c585…

Dismissing prior approval to re-evaluate 342c585