Watch vendor changelogs for breaking changes
New changes and deprecations in the APIs and tools you depend on, with the dates and the work they need.
- On a schedule: Every Monday at 8:00
What it does
The task
Open the changelogs, release notes and deprecation pages of vendors. Find the entries published since the last run. Keep the ones that affect the features that we use: features. For each one, give the vendor, the change, the date it takes effect, whether it breaks our use, and the work that it needs, with the link. Send me the breaking changes first.
- It works in any website and GitHub, in the workspace you pick, and signs in with passwords from your Cuiar vault.
- As a routine it runs every Monday at 8:00 (cron
0 8 * * 1).
What you give it
| Blank | What to give | Example |
|---|---|---|
| vendors | The vendors, with links to their changelogs | Paylane API, Shipwell, Notifyr SMS |
| features | The features and API versions that you use | Paylane charges API v2, Shipwell label API, Notifyr webhooks |
What you get back
An example run with the example values above. Your run uses your own data.
Changes that affect you: 2 of 11 new entries
- Paylane: the charges API v2 stops on 1 Mar 2027. Breaking: your checkout uses it. Work: move to the payments API v3, about 3 days. Link
- Notifyr: webhook signatures change to SHA-256 on 15 Jan 2027. Breaking: your signature check fails after that date. Work: change one function and test it, about 2 hours. Link
Not breaking: Shipwell adds 2 new carriers to the label API. Link
8 entries do not affect your features.
Run it in Cuiar
- 01
Open it
Click Use in Cuiar on this page. The side panel opens with the task in the composer.
- 02
Fill in 2 blanks
Type vendors and features. Tab moves to the next blank.
- 03
Run it, then repeat it
Run sends it once. To run it every Monday at 8:00, make a routine on cuiar.com/routines or with the CLI below.
As a routine, from the terminal
cuiar routines create "Watch vendor changelogs for breaking changes" --schedule "0 8 * * 1" --time-zone Europe/Berlin \
"Open the changelogs, release notes and deprecation pages of Paylane API, Shipwell, Notifyr SMS. Find the entries published since the last run. Keep the ones that affect the features that we use: Paylane charges API v2, Shipwell label API, Notifyr webhooks. For each one, give the vendor, the change, the date it takes effect, whether it breaks our use, and the work that it needs, with the link. Send me the breaking changes first."Run it from your AI agent
Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call create_routine yourself.
1. Add Cuiar to Claude Code
claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp2. Ask your agent
Use the Cuiar tool create_routine to run my "Watch vendor changelogs for breaking changes" template with vendors = Paylane API, Shipwell, Notifyr SMS; features = Paylane charges API v2, Shipwell label API, Notifyr webhooks.Setup for other agents: AI agents.
The tool call
{
"name": "create_routine",
"arguments": {
"name": "Watch vendor changelogs for breaking changes",
"task": "Open the changelogs, release notes and deprecation pages of Paylane API, Shipwell, Notifyr SMS. Find the entries published since the last run. Keep the ones that affect the features that we use: Paylane charges API v2, Shipwell label API, Notifyr webhooks. For each one, give the vendor, the change, the date it takes effect, whether it breaks our use, and the work that it needs, with the link. Send me the breaking changes first.",
"schedule": "0 8 * * 1",
"time_zone": "Europe/Berlin"
}
}Related templates
All monitoring templatesMonitoring
Watch security advisories for the software we use
New vulnerabilities in the products and versions that you run, with the severity and the fixed version.
On a schedule: Every weekday at 8:00- GitHub
- Any website
- Google Sheets
Engineering
Sort the security alerts in your repositories
Open Dependabot alerts across your repos, grouped by package, with the fix version and any open fix PR.
On a schedule: Every Monday at 9:30- GitHub
Engineering
List pull requests that wait for review
Open PRs across your repos with age, reviewers and CI status, the oldest first.
On a schedule: Every weekday at 10:00- GitHub
OpsAsks first
Remove a former employee's access to your tools
Every account the person still has, closed after your approval, with their files moved to a new owner.
You start it: When you start it- Any admin panel
- Google Drive
- SSlack
- +1 more: GitHub
Data
Collect stats for a list of GitHub repositories
Stars, last release, last commit, license, issues and downloads for each repository, in your sheet.
You start it: When you start it- GitHub
- npm
- PyPI
- +1 more: Google Sheets
EngineeringAsks first
Write release notes from merged pull requests
Merged PRs since the last release, grouped and written for users, saved as a draft GitHub release.
You start it: When you start it- GitHub