Weekly

Get a weekly list of your repos and tags

Every Monday you get each repository's latest tags and when they were pushed.

Runs: Weekly
Apps: Docker Hub
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every Monday at 9am, email me my Docker Hub repositories with their five newest tags and the date each was pushed.

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

Someone on a platform team is asked which image versions exist, which one was pushed last and whether the release candidate from Tuesday is actually in the registry. Answering means opening Docker Hub, clicking into each repository and reading tag lists page by page. For an organization with twenty repositories, that is a morning's work, so the question gets answered from memory and sometimes answered wrongly.

Each week the automation signs in with your access token, lists your repositories and their tags, and emails the list with the date each tag was last pushed. The result is a compact inventory of what exists in your Docker Hub account, delivered without anyone opening the site.

Release managers, DevOps leads and open-source maintainers use it to keep an eye on what is published.

What you get out of it

An inventory you did not have to build
A weekly list of repositories and tags answers what do we have without a morning of clicking. It becomes the reference people open when the question comes up, instead of a page they have to rebuild from scratch.
Unexpected pushes get noticed
A tag pushed by someone you did not expect, or on a day nothing was supposed to ship, stands out in a list of last-pushed dates. That is an early sign of a mistake or an unauthorized publish.
Release readiness checks are quicker
Before a launch, you can confirm from the latest email that the final version tag exists and was pushed when you thought. That avoids last-minute surprises during a rollout, when nobody wants to be searching a registry.
Forgotten repositories surface
A repository whose last push was two years ago appears at the bottom of the list. It prompts a decision to archive it or confirm it is still supported, rather than letting it age unnoticed on your public page.
Audit evidence of what was published
A dated email each week forms a record of the images available at that time. That helps when a customer asks which version they were running on a given date, or when a security review asks what was public.

How it works

What happens, step by step

Every Monday, ClickRuntime signs in to Docker Hub with your access token.
It lists each of your repositories and the latest tags in it, with the date each was pushed.
You get one email grouped by repository, newest tags first.

Before it runs live

Connect Docker Hub

What you get

RunsWeekly

Get a weekly list of your repos and tagstoday, 9:00Succeeded

Email · Docker Hub tagsacme/api v2.14.0 pushed 2026-10-17 v2.13.2 pushed 2026-10-09

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 Docker Hub 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_weekly_report_of_tags.pyexample

from clickruntime import on_trigger, credentials, http, notify

NAMESPACE = "acme"
HUB = "https://hub.docker.com/v2"

@on_trigger
def run(event):
    token = http.post(f"{HUB}/auth/token", json={"identifier": NAMESPACE,
                      "secret": credentials.secret("DOCKER_HUB_TOKEN")}).json()["access_token"]
    headers = {"Authorization": f"Bearer {token}"}
    repos = http.get(f"{HUB}/namespaces/{NAMESPACE}/repositories", params={"page_size": 100},
                     headers=headers).json()["results"]
    lines = []
    for r in repos:
        tags = http.get(f"{HUB}/namespaces/{NAMESPACE}/repositories/{r['name']}/tags",
                        params={"page_size": 5, "ordering": "last_updated"}, headers=headers).json()["results"]
        lines.append(f"{NAMESPACE}/{r['name']}")
        lines += [f"  {t['name']}  pushed {(t.get('tag_last_pushed') or t['last_updated'])[:10]}" for t in tags]
    notify.email_me("Docker Hub tags this week", "\n".join(lines))
    return {"repos": len(repos)}

FAQ

Common questions

What fields are included for each tag?

Each entry shows the repository, the tag name and the date it was last pushed, and can include the image size. Tell your AI assistant if you also want the digest or the last-pulled date added to the email.

Does it include private repositories?

It includes any repository the access token can read, public or private. A token tied to an account with access to your organization's private repositories will list those as well, so be careful who receives the email.

How is this different from the stale tag report?

This report lists everything with its last-pushed date, so it describes what exists. The stale tag report only lists tags nobody has pulled recently, so it is aimed at cleanup rather than at keeping an inventory.

What permissions does it need?

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.

Weekly