What this is
Platform Changelog tracks what ships in platform engineering, developer experience and DevOps, and says in plain English what it changes for the team that runs the platform. It is vendor-neutral and not affiliated with any project or company it covers.
Pipeline
Entries come only from an allow-list of public sources: project release notes, foundation and project blogs, a small number of trade publications, and items an editor adds by hand. We do not accept submitted press releases. Every entry links to its original.
What software does, and what a person does
Software fetches the sources and discards noise: pre-releases, nightly builds, chart tags, off-topic posts, and releases whose notes contain only dependency bumps, CI or docs changes. Every line of a release's notes is sorted into a change type by fixed rules, so the change lists on tool pages are the project's own words. A language model then writes a short summary and a line for platform teams.
Entries are published automatically, without an editor reading them first. Before anything goes live, fixed rules hold back any entry with a missing source link, runaway length, markup or hype vocabulary. An editor reads the feed after publication and corrects or removes mistakes. Practical notes on tool pages are written by a person, never by the model.
Change types
The vocabulary is Keep a Changelog with one flag. A line is added, changed, deprecated, removed, fixed or security, plus maintenance for dependency, CI, test and docs lines and other when the notes give no signal. Any line can carry the breaking flag, shown as the ! in the first column.
Impact tags
Major means a breaking change, a security fix in the tool itself, a capability platform teams will plan around, or a report with new primary data. Only an editor tags an entry major; everything published automatically is notable. A vendor's claims about its own product are reported as claims.
Sponsorship
Sponsored placements, when they exist, are labelled, visually separate from entries, and never carry an impact tag. Sponsors cannot buy, edit or veto coverage, and never appear on the page of a product they sell or compete with.
Provenance
Every entry a model wrote says which model wrote it and which version of our prompt it used, for examplewritten by claude-haiku-5-5, prompt 3f2a9c1. Entries are written by Claude Haiku; when it fails or declines, the same item is retried on the next larger Claude model, and only if both fail on a backup provider. Every call is logged with its cost and outcome, a stronger model grades a sample of published entries each week, and an editor sees every correction. Entries written by a person carry no such line.
Corrections
If we got something wrong, write to [email protected] and we will fix it and note the correction on the entry. Tips on public postmortems and case studies go to the same address.
# release notes are typed by code; the summary by a model tool: "kyverno" version: "v1.19.0" date: "2026-08-20" kind: "minor" # from the previous version source: "https://github.com/kyverno/kyverno/releases/tag/v1.19.0" status: "published" # queued | published | held | logged changes: - type: security text: "Limit intermediate certs to mitigate CVE-2026-32280" - type: added text: "Add updaterequest total gauge metric" - type: maintenance text: "Bump github.com/rs/zerolog from 1.35.0 to 1.35.1" # types added | changed | deprecated | removed | fixed | security maintenance | other # flags breaking: bool