ENGINEERING

Weekly stale dependency-bump digest to Slack

On a weekly schedule, gathers all open dependency-update PRs, ranks them by blast radius and age.

CategoryEngineering
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionFetch all open dependency-update PRsGitHubGitHub
  • LogicScore by blast radius and PR age
  • LogicGroup ranked PRs by owning team
  • OutputPost per-team prioritized digest to SlackSlack

What it does

Runs weekly to find every open dependency-update pull request across your repositories. For each one it computes blast radius (how many services the bumped package touches) and age, then groups the PRs by owning team and posts a ranked digest to that team's Slack channel. High-impact, long-stale bumps float to the top so they stop being ignored.

When to use it

Use it when dependency PRs accumulate faster than they merge and no one has a single view of what is rotting. A standing weekly digest per team turns the backlog into an actionable, owner-scoped list.

How it works

  1. 1A weekly schedule fires the workflow.
  2. 2All open dependency-update PRs are fetched from GitHub.
  3. 3Each PR is scored by affected-service count and days open.
  4. 4PRs are grouped by the owning team derived from code owners.
  5. 5A ranked, per-team digest message is formatted.
  6. 6The digest is posted to each team's Slack channel with direct PR links.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.