DeprecateWatch

Method, sources and limits

DeprecateWatch is a static archive. It does not call an API at page load, run a database, or guess a date. This page explains exactly where each number comes from and what it does not claim.

Pipeline

  1. Collect. Every source below is fetched once a day by a scheduled job, without an API key, and the raw response is kept unchanged.
  2. Normalise. Cycles, support-end and EOL dates are copied into one schema. A status is computed by comparing the source date with the snapshot date: supported, security-only, eol, or no-eol-date.
  3. Publish. The tables you see, the JSON API and llms.txt are generated from that one file, so the HTML, the JSON and the sitemap cannot drift apart.
  4. Verify. A test suite checks the generated site before it is published: date formats, status/date consistency, JSON schema, duplicate pages, link targets and the FAQ text used in structured data.

Sources

SourceURLUsed forTerms
endoflife.date API v1https://endoflife.date/docs/apiproduct cycles, support and EOL datesMIT (endoflife.date contributors)
AWS Lambda runtimes (deprecated runtimes table)https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimesLambda runtime deprecation datesAWS documentation
Google Cloud release notes feedhttps://cloud.google.com/release-notesdeprecation notesGoogle Cloud documentation
AWS What's New feedhttps://aws.amazon.com/new/retirement announcementsAWS
GitHub releases feedshttps://github.combreaking changes in release notesrespective projects

The endoflife.date API is MIT licensed; its copyright notice is reproduced in the footer of every page. Vendor documentation and release feeds remain the property of their vendors and are quoted with a link to the original.

What the statuses mean

What this site does not do

Snapshot

Generated (Asia/Seoul) with 489 products, 9,417 cycles, 33 Lambda runtime entries and 31 announcements.