Skip to content

Daily

Get a daily digest of new releases for the tools you use

Each morning, new GitHub releases for the repositories you follow are summarised and sent to Slack and Telegram.

Runs
Daily
Apps
Slack, Telegram
AI
Yes, uses the built-in AI allowance
Access
Telegram bot token; Slack chat:write

Send this to your assistant

Create a ClickRuntime automation: every morning, check these GitHub repos for new releases, summarise the changelogs and send the digest to #eng in Slack and to my Telegram.

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

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

Why use it

Why teams use this automation

A small engineering team depends on a dozen open-source libraries and tools. Breaking changes and security fixes are announced in release notes that nobody has time to watch, so they find out about a deprecated option when the build fails.

One morning digest with a plain summary of each new release lets the team spot what matters for them in a couple of minutes, in the chat apps they already read.

What you get out of it

  • Security fixes are not missed

    A release that patches a vulnerability shows up in the next morning's digest. The team can upgrade before it becomes a problem.

  • Breaking changes are flagged early

    The summary calls out removed options and changed behaviour. Upgrades can be planned instead of discovered during an outage.

  • Short summaries instead of long changelogs

    Each release is reduced to the few lines that matter. Reading the digest takes minutes, not an hour of clicking through release pages.

  • Quiet days stay quiet

    Releases already reported are remembered, and nothing is sent when there is nothing new. The digest only appears when it has something to say.

How it works

What happens, step by step

  1. Every morning, ClickRuntime checks each GitHub repository on your list for its latest releases.

  2. Releases it has already reported are skipped, and nothing is sent on days with no new releases.

  3. AI summarises each new release's notes in a few lines, flagging breaking changes and security fixes.

  4. The digest is posted to your Slack channel and sent to your Telegram chat.

Before it runs live

  • Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
  • Connect Telegram

What you get

RunsDaily
Get a daily digest of new releases for the tools you usetoday, 9:00Succeeded
Slack · #engpallets/flask 3.1.1: fixes a session cookie security issue; no breaking changes. Upgrade recommended.

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
  • Change what the AI looks for, or how it writes the result
  • Add another app, for example also send it to Google Sheets
  • Combine it with other Slack and Telegram 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.
release_update_digest.pyexample
from slack_sdk import WebClient
from clickruntime import on_trigger, credentials, http, state, ai, report_fetched

REPOS = ["psf/requests", "pallets/flask", "tiangolo/fastapi"]
TELEGRAM_CHAT = "your-telegram-chat-id"

@on_trigger
def run(event):
    seen = set(state.get("seen") or [])
    new = []
    for repo in REPOS:
        for r in http.get(f"https://api.github.com/repos/{repo}/releases", params={"per_page": 5}).json():
            if not r["draft"] and not r["prerelease"] and str(r["id"]) not in seen:
                new.append((repo, r))
    report_fetched(len(new))
    if not new:
        return {"summary": "No new releases"}
    parts = []
    for repo, r in new:
        try:
            s = ai.generate(f"Summarise in 2-3 lines, flag breaking changes and security fixes:\n{(r['body'] or '')[:4000]}", max_output_tokens=150).text.strip()
        except ai.AIError:
            s = (r["body"] or "")[:300]
        parts.append(f"*{repo} {r['tag_name']}*\n{s}\n{r['html_url']}")
        seen.add(str(r["id"]))
    digest = "Release digest\n\n" + "\n\n".join(parts)
    WebClient(token=credentials.connection("slack", "work")).chat_postMessage(channel="#eng", text=digest)
    http.post(f"https://api.telegram.org/bot{credentials.secret('TELEGRAM_BOT_TOKEN')}/sendMessage", json={"chat_id": TELEGRAM_CHAT, "text": digest[:4000]})
    state.set("seen", sorted(seen)[-1000:])
    return {"summary": f"{len(new)} releases"}

FAQ

Common questions

How do I choose which repositories to follow?
You list them as owner/name pairs, such as psf/requests. Adding or removing one is a one-line change to the list.
Are pre-releases included?
No, only full releases are included by default. Pre-releases and drafts can be included if you want early warning of upcoming changes.
Does it need a GitHub account?
Public repositories can be checked without one, though a GitHub token raises the request limit. Private repositories need a token with read access.
What permissions does it need?
Telegram bot token; Slack chat:write. Nothing else in your accounts is used.
Does it need AI?
Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.
How many runs does it use?
One run each time it runs (daily). 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.

Set up “Get a daily digest of new releases for the tools you use” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.