[ghost]

Related GitHub Issue

No linked issue. This is a small process change requested by the maintainers in Discord.

Description

Reworks the weekly release workflow (renamed from release-reminder.yml to release-kickoff.yml):

• The workflow posts the weekly release kickoff. The message pings the on-deck maintainer first, then @mentions zoomote as the visible cue of who cuts the release. A live webhook test confirmed webhook-posted mentions do not trigger Roomote, so the release prep runs from the separate Roomote automation at the same time. The zoomote Discord user ID is hardcoded in the workflow; it is not sensitive, so no secret is needed.
• The maintainer ping is the reminder half of the message. A new repo secret, DISCORD_RELEASE_MAINTAINERS, holds space-separated Discord user mentions in the <@USER_ID> form. The rotation pings one maintainer per week, anchored to 2026-07-17 (same anchor as the previous Elliott / James / Toray rotation). Falls back to a generic "Maintainers" greeting if the secret is unset.
• The maintainer reminder lists the manual steps that remain after the release PR opens: review/approve, tag the release branch, approve the marketplace-production deployment, merge queue.
• The webhook payload sets allowed_mentions to parse user mentions, so the <@USER_ID> pings render as real pings (verified with a live webhook test).
• Moves the schedule to Friday at 7:00pm ET (23:00 UTC; fires at 6:00pm ET while the US is on EST).

Reviewers should check:

• The webhook secret DISCORD_RELEASE_WEBHOOK_URL now points at a webhook for the release channel (maintainer action outside this PR).
• The mention format in DISCORD_RELEASE_MAINTAINERS uses numeric user IDs (<@123...>), not @Handles. Only that form pings users in Discord.

Test Procedure

• YAML syntax checked by review. The workflow is otherwise unchanged in structure.
• After merge and after the two secrets are set, run the workflow manually with workflow_dispatch and confirm:
  1. The message posts in the release channel and pings the on-deck maintainer.
  2. Both pings render in the channel: on-deck maintainer first, zoomote second. The Roomote release prep is driven by the standalone Roomote automation; the zoomote mention line stays as a visible cue.

Pre-Submission Checklist

• Issue Linked: No issue. Small maintainer-requested process change.
• Scope: Workflow rename and message rework only.
• Self-Review: I reviewed my own code with care.
• Writing Style: The PR title and description use short sentences and plain words.
• Testing: Not applicable. Manual workflow_dispatch test after secrets are set.
• Visual Snapshot: Not applicable. No UI change.
• Documentation Impact: No user-facing documentation change required.
• Contribution Guidelines: I read and agree to the Contributor Guidelines.

Visual Snapshots

Not applicable.

Videos (interaction / animation only)

Not applicable.

Documentation Updates

• No documentation updates are required.

Additional Notes

Required maintainer actions after merge:

1. Update the DISCORD_RELEASE_WEBHOOK_URL secret with a webhook for the release channel.
2. Add the DISCORD_RELEASE_MAINTAINERS secret, for example: <@123456789012345678> <@987654321098765432>

Get in Touch

Roomote (zoomote) on Discord.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: Zoo-Code-Org/Zoo-Code/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 7c69c843-3981-43e7-9b0c-dd6c95a7f6e3

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

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

Review status

This PR was opened by an automated account. A human maintainer must verify the change intent, provenance, and validation before merging.

Current step: Required CI passed. Waiting for automated review of the latest commit.

If automated review does not start, a maintainer must restart it.

Review-state labels are managed by this workflow; do not edit them manually. community-approved is managed the same way — do not add or remove it manually. It signals a fresh community code approval for the current head as an advisory priority only; maintainer review is still required.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!