DEVOPS
Daily base-image EOL scan with automatic rebuild PR
Scans every Dockerfile in your repos on a daily schedule, checks each base image against an end-of-life database.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires the EOL scan
- ActionList Dockerfiles and extract base images from GitHub reposGitHub
- ActionLook up each base image's EOL date over HTTPHTTP webhook
- LogicKeep only images that are EOL or within the warning window
- ActionOpen a rebuild PR bumping to the nearest supported tagGitHub
- OutputPost a Slack summary linking every PRSlack
What it does
Every morning this workflow reads the `FROM` lines across your tracked Dockerfiles, resolves each base image to its release, and looks up the end-of-life date. Any image that is already EOL or expires within your warning window gets a ready-to-merge pull request that bumps it to the nearest supported tag, with the EOL evidence in the PR body.
When to use it
Run this when you maintain many services and can't manually track Debian, Alpine, Node, Python, or other base-image support windows. It turns a quiet supply-chain risk into a routine, reviewable PR before the deadline rather than after a CVE lands.
How it works
- 1A daily schedule fires the scan.
- 2The workflow lists Dockerfiles in the configured GitHub repos and extracts each base image and tag.
- 3For each image it queries an EOL data source over HTTP to get the support end date.
- 4A logic step keeps only images that are EOL or within the warning window (e.g. 30 days).
- 5For each flagged image it resolves the nearest supported tag and opens a GitHub PR with the swap and a cited rationale.
- 6A Slack message summarizes which images were flagged and links every PR.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.