API Changelog Brief

Method and coverage

This issue lists changes published 2026-09-05 to 2026-10-05. Every page was read on 2026-10-05. Only the vendors' own public changelog, release-notes and deprecations pages were used.

Pages read

The changelog index of each vendor was read, then the entry page of each change where the vendor has one.

How the entries were checked

These pages are built from one data file of 142 entries. A validation script exists for that file: it checks that every entry has all its fields, a date inside the range, a known type, a deadline that is empty or a valid date, and a source address that is https and on the vendor's own domain, and it rejects duplicates. For this build the script was not run and no JSON parser read the file. An AI agent tallied the entries by reading the file, then cross-checked with pattern searches: each of the 142 entry lines matches the expected fields, vendor, date range, type and source domain, and the number of rows on each vendor page equals the number of entries for that vendor in the data file (68, 43, 16 and 15). The source addresses were not tested for availability. None of this judges whether a summary is accurate; that is why each entry should be verified against the official changelog.

Coverage gaps

Caveats