Changelog Monitor
Watch the docs page and GitHub release notes. Get told when an API actually changes.
A changelog monitor watches docs and GitHub so an API change does not surprise production.
The launch tweet is optional. The break is a renamed field in a docs commit that shipped while you slept. GitHub watch mail does not save you. It dumps every tag, every typo fix, and every "thanks for the PR" note into a folder you stopped opening months ago.
What a changelog monitor should catch
You care about substance. A removed endpoint. A header that used to be optional. A price row that moved. A deprecation date with a cutoff. A sidebar restyle is noise. So is a hiring post that happens to live on the same URL as the notes.
GitHub release alerts cover tagged versions. A changelog monitor is the other half. Many vendors never tag. They edit a markdown page and move on. Stripe, Twilio, and GitHub keep a public changelog. Labs bury the same facts in API docs. Paste whichever URL actually moves. AyeWatch watches public pages and topics. It does not sit inside your repo and it does not parse your lockfile.
How to set one up
Paste the HTTPS changelog or docs URL. Write the rule the way you would Slack a teammate. "Tell me when endpoints, request fields, auth, or pricing change. Ignore nav and typos." If there is no clean page, describe a topic instead. Cover the library name plus "breaking change" and the docs host you trust.
Use push if you ship on that API tonight. Use email if morning is fine. Free Preview is six lifetime runs across three topics. Pro is $9 a month. Paid plans add the API and webhooks, so a changelog ping can open a ticket. See webhook monitoring pipelines if you want that path. Start from monitoring templates or the developers page if you would rather not invent the wording.
Start a monitor in under a minute
Free Preview is six lifetime runs across three topics. No card.
Try AyeWatch freeWhen RSS is enough
If the vendor already publishes a clean RSS changelog and you read it every morning, keep the reader. Add AyeWatch when the changelog is a docs page with no feed, or when you also want GitHub and HN coverage of the same break. License flips belong on a LICENSE file watch. Read how to monitor open-source licenses for that case. Model drops belong on LLM alerts if the page you care about is a lab blog, not a REST reference.
Start with the page that already burned you
Pick one dependency that already surprised production. Point AyeWatch at that URL first. If the first alert names the real change, add the next page. Do not boil the ocean on day one. Three topics is the Free Preview cap. Spend them on the APIs you cannot afford to miss, then upgrade when the quiet docs edit is the one you needed.