Daily Docker Hub new-image digest for your Slack channel
Every weekday morning, get a clean Slack summary of which Docker Hub images picked up new tags in the last day, grouped by repository.
Docker Hub
SlackEngineeringOperationsNotifications & AlertsDaily DigestsEvery weekday at 9am, check my Docker Hub account for images that received new tags in the last 24 hours and post a summary to Slack. If nothing was pushed, skip the message so the channel stays quiet.
First, enumerate my repositories with Docker Hub's List Repositories in a Namespace, using my Docker ID (or organization name) as the namespace, and page through all results. For each repository, call List Repository Tags and keep only tags whose tag_last_pushed timestamp falls within the last 24 hours. Docker Hub timestamps are ISO 8601 UTC.
Group the surviving tags by repository. For each repository, list the new tag names and their push times, and call out notable version jumps, such as a major bump like 1.x to 2.0 or a new 'latest' tag pointing at a fresh image.
Post one tidy message to the #releases channel using Slack's Send a Message, formatted with Slack mrkdwn: a short header, then one section per repository with its new tags, kept scannable. If no repository received a new tag inside the window, do not post at all.
Example output
Additional information
What does this prompt do?
- Checks your Docker Hub account every weekday morning for images that received new tags in the last day.
- Groups the new tags by repository and highlights notable version jumps so you can see what actually changed.
- Posts one tidy summary to a Slack channel like #releases, formatted to be quick to scan.
- Stays quiet on days when nothing was pushed, so the channel only lights up when there's real news.
What do I need to use this?
- A Docker Hub account with the repositories you want to watch.
- A Slack workspace and a channel to post into (for example #releases).
- A posting time that fits your team, with 9am on weekdays as the default.
How can I customize it?
- Change the schedule or timing, for example post at 8am or widen the window to 72 hours on Mondays so weekend pushes are not missed.
- Point it at a different Slack channel, or send the summary to more than one.
- Adjust what counts as notable, such as only flagging major version bumps or new 'latest' tags.
Frequently asked questions
Will it post if nothing new was pushed?
Can it watch an organization's repositories, not just my personal ones?
What does the Slack message look like?
Can I run it more or less often?
Do I need to set anything up inside Docker Hub?
Related templates
Stop refreshing Docker Hub to see what shipped.
Let this workflow watch your repositories and drop a tidy release summary in Slack every morning.