GitHub releases to a sheet
Logs each repo's weekly releases as rows in a Google Sheet, so nothing slips.
Every Monday, build a running release log in Google Sheets from the GitHub repos I track. Use the **github** connection to read releases and the **googlesheets** connection to append them. Repos to watch: - vercel/next.js - facebook/react - <add the repos and dependencies your team actually ships on> Steps: 1. In **googlesheets**, open the spreadsheet named "Release Log" (create a tab called "Releases" with the header row Date | Repo | Version | Highlights | Breaking? if it isn't there yet). Read the existing rows first so you know the latest version already logged for each repo — never append a release that's already in the sheet. 2. For each repo, use **github** to fetch releases published in the last 7 days (skip drafts and pre-releases unless I list one explicitly). Skip any repo with no new release. 3. For each new release, append one row to the "Releases" tab: - Date — the release's published date (YYYY-MM-DD) - Repo — owner/name - Version — the tag (e.g. v16.3.0) - Highlights — 1–2 tight sentences on what actually matters, breaking changes first - Breaking? — "Yes" if the notes flag a breaking change or required migration, else "No" Append in date order, oldest first, so the log reads top-to-bottom. Then reply with a short summary: how many releases you logged, which repos, and call out by name any row where Breaking? = Yes. If there were no new releases, say "No new releases this week — nothing logged" in one line and don't touch the sheet. Keep the reply under 10 lines and skimmable.
Release log updated — week of 30 Jun 2026 Logged 3 new releases to the "Releases" tab: • vercel/next.js — v16.3.0 (28 Jun) — Breaking ⚠️ • facebook/react — v19.2.0 (26 Jun) • prisma/prisma — v6.4.1 (24 Jun) Heads up: next.js v16.3.0 is breaking — `images.domains` removed, migrate to `remotePatterns`. The sheet now has 47 rows. Nothing else shipped this week.
How it works
- Attach your github and googlesheets connections — the routine reads each repo's releases through GitHub, then appends them as rows in your "Release Log" sheet.
- It reads the sheet first to see what's already logged, so every Monday adds only the new releases — no duplicates, no re-runs clobbering history.
- Each release becomes one skimmable row (date, repo, version, highlights, breaking?), and you get a short summary that names anything with a breaking change.
Make it yours
- List the repos your product actually runs on, and point it at your own spreadsheet and tab name.
- Add columns it should fill — author, release URL, or a "Reviewed?" checkbox your team ticks off.
- Switch to daily during a migration, or have it also email the summary by keeping "Email me the result" on.
Run “GitHub releases to a sheet” on autopilot
Copy it to your account, tweak the details, and it runs mondays at 9:00 am.
Use this routine →More Engineering templates
Each weekday, triages new, stale, and needs-triage issues across the repos you pick — grouped, prioritized, with a suggested label and owner per issue.
A Monday-morning summary of every new release across the repos and dependencies you care about.
Every Friday, scan Cloudflare's developer docs for the Workers, Pages, and security features that matter to your setup — plus recent changelog posts — emailed as a prioritized digest.
Every Monday, check Context7 for the current documented version, API, and migration notes of the libraries your project depends on — emailed as a short upgrade to-do list.