ENGINEERING
Major dependency bump triage to Linear
Detects major-version dependency bumps in Dependabot PRs, scores the blast radius across services.
How it runs
The automated pipeline, trigger to output.
- TriggerDependency-update PR openedGitHub
- ActionParse and classify version delta (patch/minor/major)
- LogicBranch: route non-major bumps to auto-merge exit
- LogicRank affected services by dependent count
- ActionCreate assigned Linear tracking issueLinear
- OutputComment the issue link back on the PRGitHub
What it does
When a dependency-update PR lands, it determines whether the bump crosses a major version boundary. Patch and minor bumps are left to auto-merge; major bumps are escalated. For each major bump it counts how many services depend on the package, identifies the most affected owning team, and creates a Linear issue with the impact breakdown so the upgrade is tracked as real work, not just a stale PR.
When to use it
Use it when automated dependency PRs pile up and major upgrades quietly rot because no one owns the migration. This forces every breaking bump into your backlog with an accountable owner.
How it works
- 1A Dependabot or renovate pull request is opened on GitHub.
- 2The version delta is parsed and classified as patch, minor, or major.
- 3A branch routes non-major bumps to a no-op exit so they auto-merge normally.
- 4For major bumps, dependent services are counted and ranked by impact.
- 5A Linear issue is created with the affected-service list and assigned to the top owning team.
- 6The PR is commented with a link back to the tracking issue.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.