Track Cypress breaking changes, release notes, and deprecations without living in update feeds.
Breaking.watch helps you follow Cypress release notes, API changes, deprecations, and security updates from official sources.
Testing stack changes matter when they affect browser behavior, runners, fixtures, CI stability, or the reliability of release gates.
The changes that make Cypress worth monitoring.
Testing stack changes matter when they affect browser behavior, runners, fixtures, CI stability, or the reliability of release gates.
The updates that usually matter are the ones that change API behavior, introduce migration work, retire old paths, or quietly shift security and auth expectations.
The roles that usually own the follow-up work.
- QA engineers
- frontend developers
- platform engineers
The kinds of Cypress updates people usually care about.
browser and runner changes
The kind of update that is easy to ignore now and annoying to deal with later.
fixture and API compatibility
The kind of update that is easy to ignore now and annoying to deal with later.
CI stability changes
The kind of update that is easy to ignore now and annoying to deal with later.
release-gate reliability impacts
The kind of update that is easy to ignore now and annoying to deal with later.
More services in Testing & QA.
A few quick questions.
Read the full FAQHow do I keep up with Cypress updates?
Breaking.watch helps you keep an eye on official Cypress release sources without having to check them by hand all week.
What kinds of Cypress updates matter most?
Usually the ones that change behavior, break compatibility, announce deprecations, or create follow-up work later.
Why not just read the Cypress changelog myself?
You can. The problem is remembering to do it consistently across everything else your stack depends on.
Can I track Cypress with related tools in the same category?
Yes. That is the whole point — keeping the tools that belong together in one place instead of scattered across a dozen tabs.