ENGINEERING
Escalate deprecations approaching their end-of-life deadline
On a daily schedule, checks open deprecation issues in Linear against known end-of-life dates, and for any still-unresolved deprecation past its warning threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionRead open deprecation issues from LinearLinear
- LogicFilter to issues nearing end-of-life
- ActionComment deadline pressure on Linear issueLinear
- OutputPage owner via PagerDuty for critical deprecationsPagerDuty
What it does
This workflow makes sure deprecations don't quietly cross their removal date. Each day it compares your tracked deprecation issues against their known end-of-life dates and escalates the ones running out of runway, so a library removal never breaks production by surprise.
When to use it
Use it when upstream dependencies announce hard removal dates and you need a forcing function as those dates approach. Best paired with the rollup or scoped-issue workflows that create the Linear issues in the first place.
How it works
- 1A daily schedule starts the run.
- 2The flow reads open deprecation issues from Linear along with their recorded end-of-life dates.
- 3A filter selects issues whose deadline falls inside the escalation window and are still unresolved.
- 4For each, it posts a deadline-pressure comment on the Linear issue with days remaining.
- 5It raises a PagerDuty notice for any deprecation past the critical threshold so an owner is paged before removal lands.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.