Weekly

See which releases introduced new errors

A Friday email listing the week's releases with the number of new issues each one brought in.

Runs: Weekly
Apps: Sentry
AI: Not needed
Access: project:releases (read), org:read

Send this to your assistant

Create a ClickRuntime automation: every Friday at 4pm, email me this week's Sentry releases and how many new issues appeared in each one.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

When a team deploys several times a week, nobody keeps a clear picture of which release introduced which problems. Sentry tracks releases and the issues that start in each one, but the information is spread across a releases page and many issue pages. At the Monday engineering meeting someone asks whether version 2.41 was a good release, and the answer is a guess based on how loud Slack was, not on how many new errors it actually brought.

Each week the automation lists the organization's releases since the last run, fetches the count of new issues introduced by each, and emails a summary. Every release is listed with its version, deploy time and new-issue count. Engineering leads and release managers use it to review quality by release instead of by impression.

What you get out of it

Release quality becomes measurable
A new-issue count per release gives a number to compare. A version that brought thirty new errors stands out against ones that brought two, and the discussion turns to evidence.
Risky changes are traced to a version
When an issue appears, knowing which release introduced it narrows the search to that release's commits. That shortens debugging time and avoids blaming unrelated changes. If 2.41 brought thirty new issues, its commits are the first place to look, not last month's.
Process improvements can be tested
If the team adds a testing step and new issues per release fall, the digest shows it. Leaders can tell whether a process change is helping without relying on feelings.
Releases are not forgotten
Hotfixes and minor releases are easy to lose track of. A weekly list reminds everyone what was shipped, which is useful for support staff trying to match a customer's report to a version.
Retrospectives start with data
A release that went badly can be reviewed with the facts in front of the group. Retrospectives are more productive when people look at counts and links rather than recollections.

How it works

What happens, step by step

Every Friday ClickRuntime lists the releases your Sentry organisation shipped since its last run.
For each release it counts the new issues that release brought in.
You get an email listing each release and its new-issue count.

Before it runs live

Connect Sentry

What you get

RunsWeekly

See which releases introduced new errorstoday, 9:00Succeeded

Email · Weekly releasesweb@2026.10.17: 3 new issues api@4.12.0: 0 new issues

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Sentry steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

get_a_digest_of_new_releases.pyexample

from datetime import datetime, timedelta, timezone
from clickruntime import on_trigger, credentials, http, notify

SENTRY = "https://sentry.io/api/0"
ORG = "acme"

def sentry(path, **params):
    resp = http.get(f"{SENTRY}{path}", params=params, headers={"Authorization": f"Bearer {credentials.secret('SENTRY_AUTH_TOKEN')}"})
    resp.raise_for_status()
    return resp.json()

@on_trigger
def run(event):
    cutoff = datetime.now(timezone.utc) - timedelta(days=7)
    lines = []
    for r in sentry(f"/organizations/{ORG}/releases/", per_page=50):
        if datetime.fromisoformat(r["dateCreated"].replace("Z", "+00:00")) < cutoff:
            continue
        detail = sentry(f"/organizations/{ORG}/releases/{r['version']}/")
        lines.append(f"{r['shortVersion']}: {detail.get('newGroups', 0)} new issues")
    notify.email_me(f"{len(lines)} Sentry releases this week", "\n".join(lines) or "No releases this week.")
    return {"releases": len(lines)}

FAQ

Common questions

How does Sentry know which issues a release introduced?

Sentry attributes an issue to the release in which it was first seen, based on the release value sent with events. If your app does not report release versions to Sentry, the counts will not be meaningful.

Does the digest include releases from all projects?

It covers every release Sentry lists for the organization, and a release shared across projects appears once; you can narrow it to chosen projects. Teams with a separate mobile and web project often keep both in one digest so version numbers can be compared side by side.

What if a week has no new releases?

The email can say that no releases were deployed, or the automation can skip sending in that case. Which is better depends on whether silence would worry you or whether you only want mail when there is news.

What permissions does it need?

project:releases (read), org:read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

On a schedule