Vendor Release Watch · Developer
Know the day a dependency ships a breaking change
It watches a vendor's releases feed, summarises each release, lists breaking changes, deprecations and security fixes as written, and flags what touches your stack in Slack.
Free account to start. Buying and running live need a paid plan.
- Starts from an event in a connected app
- 1 AI step
- About 10 min to set up
Sound familiar?
The job, before and after this agent.
What it feels like today
- “We found out about a breaking SDK change when production broke.”
- “Nobody has time to read every framework's release notes.”
- “Security fixes in our dependencies go unnoticed for weeks.”
What you get with the agent
- A vendor's JSON releases feed (for example GitHub releases for a repository) checked on your plan's schedule.
- A plain-words summary of each new release.
- Breaking changes, deprecations and security fixes listed exactly as written.
- Flags for which parts of your described stack they touch, and who owns them.
- Posted to your engineering channel in Slack; drafts and optional pre-releases skipped.
Before
A framework you depend on deprecates a config option and patches a security issue. You find out a month later from a forum thread.
After
The day the release ships, Slack shows a summary: one breaking change affecting your image handling (owner: web team), one deprecation in your config and a security fix to apply.
How it works
The whole workflow, step by step.
Watches a vendor's JSON releases endpoint, for example GitHub's releases API for a repository you depend on, on your plan's schedule interval. For each new release, AI summarises the notes and lists breaking changes, deprecations and security fixes exactly as written, then flags the ones that touch the stack you describe and who owns them. The summary is posted to your engineering channel in Slack. It only reads the public feed: one vendor per setup, JSON only (no HTML pages or RSS), and it never touches your code.
- TriggerNew release at the endpoint
- AI stepSummarise and flag what matters
- LogicPost it?
- Skip:Not posted
- Post:Post to Slack
- OutputNot posted
- App callPost to Slack
- OutputPosted
This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.
- Step 1New release at the endpointChecks the vendor's JSON releases endpoint on your plan's schedule interval and starts a run for each new release (e.g. GitHub's releases API).
- Step 2Summarise and flag what mattersAI summarises the release, flags breaking changes, deprecations and security fixes, and says which parts of your stack they touch.
- Step 3Post it?Drafts (and pre-releases, when your stack note says to skip them) are kept in the run history only.
- Step 4Not postedThe run history keeps the summary.
- Step 5Post to SlackPosts the summary, breaking changes and what they touch in your stack to your engineering channel.
- Step 6PostedThe run history keeps the release summary.
Example run
What goes in, and what comes out.
Example with fictional data
Comes in
New release v4.2.0 from a fictional open-source UI library's GitHub releases feed: one breaking change to the theme API, one deprecation, one security fix.
The agent produces
Slack: short summary; Breaking: theme API change, touches your design system (owner: front-end team); Deprecation listed as written; Security: fix in the sanitizer, recommend upgrading soon.
What you need
Everything it takes to run it.
About 10 minutes from purchase to live. A checklist above the canvas takes you through each step.
Plan
Included in Enterprise; on other paid plans it's $69 once. Agents run live on paid plans, from Basic ($39/mo).
Your AI key
Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.
Apps
- HTTP / Custom APILive
- SlackLive
Checklist
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- An HTTP / Custom API connection for the vendor's API, and Slack, connected in Settings → Integrations.
- An endpoint that returns the releases as a JSON list.
Setup, about 10 minutes
- Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
- Connect the vendor's API (HTTP / Custom API). Add an HTTP / Custom API connection with the vendor's API base URL (Settings → Integrations → HTTP / Custom API), e.g. https://api.github.com with an optional read-only token.
- Connect Slack. Connect the Slack workspace your engineers use (Settings → Integrations → Slack).
- Point the trigger at the releases. Open the trigger, pick the vendor connection and enter the releases path.
- Describe your stack. Open “Summarise and flag what matters” and replace the placeholder with your stack.
- Pick the Slack account and channel. Open “Post to Slack” and pick your account and channel.
- Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
- Switch the trigger on. Open the trigger and click “Activate app trigger”: the endpoint is checked on your plan's schedule interval. Releases published before activation aren't posted.
Is it a fit?
Who it's for, and what it won't do.
Built for
- Engineering teams depending on fast-moving frameworks or SDKs
- Tech leads and CTOs
- Platform and DevOps engineers
- Agencies maintaining many client apps
What it doesn't do
- It only reads the public releases feed: it never touches your code, dependencies or repositories.
- One vendor per setup (one HTTP connection has one base URL).
- It doesn't read HTML changelog pages or RSS feeds, only JSON.
- It reports what the notes say: it doesn't test upgrades or open tickets.
We list the limits up front so you can decide before you buy.
Price
$69 one-time
Per workspace. It never renews.
- Included at no extra cost on Enterprise.
- Buying and running it live need a paid plan, from Basic ($39/mo).
- Dry Run costs nothing: simulated AI and app calls, nothing sent.
- AI usage is billed by your own provider, at cost. No AI credits to buy from us.
One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy
FAQ
Questions about Vendor Release Watch.
Does it touch my code?
No. It only reads the public releases feed. It doesn't change your code, dependencies or repositories, test upgrades or open tickets.
Can it watch several vendors or read RSS?
One vendor per setup (one HTTP connection has one base URL); set it up again for another. It needs a JSON releases endpoint, not HTML changelogs or RSS.
How fast is setup?
About 10 minutes: an HTTP connection for the vendor's API, the releases path, a description of your stack, and Slack. To run it live you need a paid plan and your own AI provider key (OpenAI, Anthropic, Google and others), added in Settings. Dry Run on sample data is free, so you can see real output before you commit.
Is it worth the price?
It's a one-time purchase that never renews. Catching one breaking change before it hits production pays for it.
Can it watch several vendors?
One vendor per setup: each HTTP connection has one base URL. Set the agent up again for another vendor or repository.
Can it read an HTML changelog or RSS feed?
No. It needs an endpoint that returns JSON with a list of releases (GitHub releases API, or a vendor's JSON changelog).
Is this a subscription?
No. Vendor Release Watch is a one-time purchase of $69 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.
Can I test it before it touches real data?
Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.
Put Vendor Release Watch to work.
Free account, no credit card. Your Agents page opens with Vendor Release Watch ready to buy and set up, then Dry Run it before it goes live.