ENGINEERING
Watch Sentry for regressions after a dependency bump merges
After a dependency MR merges in GitLab, this watches Sentry for new error signatures tied to the bumped package's blast radius and alerts Slack the moment a likely regression…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab dependency MR merged to default branchGitLab
- ActionResolve affected modules and record watch windowPostgres
- ActionPoll Sentry for new errors in affected modulesSentry
- LogicCompare to baseline to isolate regressions
- OutputAlert Slack with MR, Sentry issue, and packageSlack
What it does
A bump can pass tests and still break in production. When a dependency MR merges, this workflow remembers which modules that package touches, then watches Sentry for new or spiking error signatures originating in those modules during a post-deploy window, and raises an alert if one appears.
When to use it
Run it when you auto-merge low-risk dependency updates and need a safety net that connects a fresh production error back to the specific bump that likely caused it, so you can roll back fast.
How it works
- 1A GitLab merge webhook fires when a dependency-bump MR is merged to the default branch.
- 2The workflow resolves the package's affected modules from the Postgres dependency graph and records a watch window.
- 3During the window it polls Sentry for new error signatures whose stack frames fall inside those modules.
- 4A logic step compares against the pre-merge baseline to isolate genuinely new regressions.
- 5On a match it posts to Slack with the offending MR, the Sentry issue link, and the suspect package.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SentryErrors, performance, releases.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.