API Deprecation Report — September 2026
What is sunsetting and when: 46 deadlines inside 30 days and 21 breaking changes, read straight off 132 vendors' own notices.
Written by
Scraper.io
Generated from the API Deprecation Watch feed
What is sunsetting and when: 46 deadlines inside 30 days and 21 breaking changes, read straight off 132 vendors' own notices.
Every number on this page is read from the API Deprecation Watch feed's 2 September 2026 run. Nothing here is typed by hand, so nothing here goes stale quietly: when the feed re-runs, the page is rebuilt from the new export.
- Deprecations tracked
- 285
- across 132 vendors
- Sunsetting in 30 days
- 46
- 141 inside 90 days
- Breaking severity
- 21
- client-side rewrite required
- New this run
- 21
- dated in the 7 days to 2 September 2026
The next deadlines
46 of the 285 tracked deprecations sunset inside the next 30 days, and 141 inside 90. Those are the ones worth putting in front of an engineering lead this week; everything past that window is planning, not triage.
The soonest deadline in the run is devuan 4, 1 day out.
- devuan 4 — 2026-08-15 (1 day)
- mattermost 10.11 — 2026-08-15 (1 day)
- traefik 3.6 — 2026-08-16 (2 days)
- grafana 12.3 — 2026-08-19 (5 days)
- numpy 2.1 — 2026-08-19 (5 days)
Breaking changes, not just end-of-life
21 notices in this run are classified breaking: the vendor is changing behaviour callers depend on, rather than simply retiring a version on a published schedule. The remaining 264 are material — scheduled, but recoverable with a version bump.
Severity is read from the notice itself, not inferred from the product. A breaking label always has the vendor's own page behind it.
Where the pressure sits
Inside the 90-day window the deadlines cluster on azure (5), cakephp (4), oracle (4), rocket-chat (4) and aws (3).
Across the whole run 132 vendors are represented, so a single upgrade sprint rarely clears more than one of them at a time.
- azure — 5 deadlines inside 90 days
- cakephp — 4 deadlines inside 90 days
- oracle — 4 deadlines inside 90 days
- rocket-chat — 4 deadlines inside 90 days
- aws — 3 deadlines inside 90 days
How to read the date basis
Every row carries how its date was established: 244 stated by the vendor, 40 taken from an announcement, 1 derived from a support policy. A derived date is an inference from a published lifecycle rule, and it is labelled that way rather than presented as a commitment.
That distinction is the point of the column. A stated sunset can be diarised; a derived one should be confirmed with the vendor before anyone plans a migration around it.
| Product | Vendor | Sunset | Days left | Severity | Date basis |
|---|---|---|---|---|---|
| devuan 4 | devuan | 2026-08-15 | 1 | Material | Stated |
| mattermost 10.11 | mattermost | 2026-08-15 | 1 | Material | Stated |
| traefik 3.6 | traefik | 2026-08-16 | 2 | Material | Stated |
| grafana 12.3 | grafana | 2026-08-19 | 5 | Material | Stated |
| numpy 2.1 | numpy | 2026-08-19 | 5 | Material | Stated |
| gitlab-runner 19.0 | gitlab-runner | 2026-08-20 | 6 | Material | Stated |
| gitlab 19.0 | gitlab | 2026-08-20 | 6 | Material | Stated |
| bamboo 10.0 | bamboo | 2026-08-21 | 7 | Material | Stated |
| jira-software 10.0 | jira-software | 2026-08-22 | 8 | Material | Stated |
| cortex-xdr 9.0 | cortex-xdr | 2026-08-23 | 9 | Material | Stated |
Product names link to the source the sunset date was observed on. Days left are counted from the run date, not from today.
Get this as a live feed
This page is one run of API Deprecation Watch. The feed is the product.
The table above is a slice. Open the feed for every row, filter it to the vendors or companies you care about, and take the change as a delivery instead of re-reading a post.
Provenance
- Last run
- 2 September 2026
- Rows in run
- 285 published, 0 withheld by the sanity filter
- Feed
- API Deprecation Watch
- Sources
- Sunset dates come from vendor end-of-life pages, release notes and lifecycle policies. Each row keeps the URL it was observed on.
Generated from the API Deprecation Watch export dated 2 September 2026. Every published value keeps the URL it was observed on, and rows whose numbers or identities did not survive the sanity filter are withheld rather than corrected — the count is stated above so the denominator is never hidden. Nothing on this page is written or estimated by a model.
This report is a rendering of a live feed, not a hand-written round-up. When the feed re-runs, the counts, the deadline list and the table below all move with it — and the previous numbers stay reproducible from the export they were built on.