GitHub Release and Issue Digest

Answer first: List the repos you depend on and ask Grok Bot: "Every Monday at 9:00 AM, summarize new releases and notable issues in these repos." It reads public GitHub data, flags breaking changes, and posts a digest. For instant alerts, a routine can be triggered by GitHub events instead.

Test status: tested on 2026-10-16 with the public GitHub API from the box. cli/cli returned releases v2.102.0 (2026-09-30) and v2.101.0 (2026-09-15). python/cpython returned no releases: it publishes tags (its tag feed showed v3.16.0a1), which is a real gotcha. The routine was not scheduled.

Who it's for

Developers and engineering managers who keep finding out about breaking changes too late.

Steps

1. List the repos as owner/name.
2. Check whether each one publishes Releases or only tags. The digest prompt handles both.
3. Paste the prompt. For event-driven alerts on your own repos, connect GitHub and ask for a GitHub-triggered routine.

Copy-paste prompt

Every Monday at 9:00 AM, for each repo in <owner/repo, owner/repo, ...>:
list releases published in the last 7 days (if the repo has no Releases, use new tags instead).
Summarize each in 2 lines, and flag anything mentioning "breaking", "deprecat", "security", or "migration".
Also list issues opened in the last 7 days with the most comments (top 3).
Post a digest here, grouped by repo, with links. Say "no changes" for quiet repos.

Expected result

A weekly digest by repo, with breaking-change flags and links.

Gotchas

• Releases vs tags: repos like CPython return an empty releases list. Always fall back to tags.
• Unauthenticated GitHub API calls are rate-limited. A weekly run over about 10 repos is fine, but hourly runs over many repos may hit the limit.
• Pre-releases (alpha, rc) show up too. Ask it to skip them if you only want stable releases.

FAQ

Private repos? Connect GitHub when it shows the connect card. Public repos need no connection.