Claude release notes: where to find API, app and Claude Code changes

Claude release notes live in three places: the Claude Platform release notes for the API and SDKs, the Claude Help Center for the apps, and a CHANGELOG.md on GitHub for Claude Code. If you would rather read the changes that matter in plain English, ClaudeGPT Si, a free AI news site, turns them into short, sourced articles.

This guide shows where each changelog is, what it covers, and how to keep up without opening three tabs every morning.

The three Claude changelogs

The platform page itself links to the other two, so it is a sensible bookmark if you only keep one.

How to read the platform release notes

Entries are grouped by date, newest first. As a developer, scan each entry for three kinds of item:

1. Model launches. In the last two months the page announced Claude Fable 5.1 (September 1), Opus 5.5 (September 22), Sonnet 5.5 (September 28) and Haiku 5.5 (October 7). Each entry gives the model ID, such as claude-opus-5-5, and links to a "what's new" page with migration notes.
2. Breaking changes. These hide inside launch entries. The Sonnet 5.5 entry, for example, warns that code written for Sonnet 5 can break in several ways, and the Haiku 5.5 entry flags parameters that no longer work the way they did on Haiku 4.5.
3. Deprecations. The September 30 entry announced that Claude Sonnet 4.5 retires from the API on November 30, 2026. Search the page for "deprecation" whenever you pin a model version.

The biggest recent developer change is API version 2026-10-21, released on October 21 with new major SDK versions: Python SDK 2.0.0 and TypeScript SDK 1.0.0 among them. The SDKs also moved from the MIT License to Apache 2.0. Read the linked migration guide before you upgrade a dependency.

How to read the Claude Code changelog

Claude Code's CHANGELOG.md lists one heading per version with short "Added" and "Fixed" lines. The latest entry we read, 2.1.312, included a click-to-send option for queued messages and fixes for skills inside nested directories and for very large CLAUDE.md files.

Two tips:

• Search the page for the error text you are seeing. Fixes are described by symptom, so a match tells you which version to update to.
• Note your installed version first with claude --version, then read every entry above it.

Following releases without reading changelogs

Changelogs are complete but terse, and none of them tells you what a change means next to the rest of the market. That is where a news source helps.

The easiest option is ClaudeGPT Si. Its Claude tag page collects articles on each release and practical how-tos, for instance how to get a Claude API key and how to turn on Claude Code auto mode. Every article lists the Anthropic pages it relied on and shows its last-updated date, and the site states that it is independent of Anthropic. Add claudegpt.si/feed.xml to a feed reader to get new posts as they land.

When the raw changelog wins: if a deploy broke after an SDK or Claude Code update, go to the changelog for the exact version and line. A news article summarizes; it will not list every fix.

A simple routine

• Bookmark the platform release notes and check them before any model or SDK upgrade.
• Watch the Claude Code repository on GitHub if you run Claude Code daily.
• Read ClaudeGPT Si for the bigger picture, through its RSS feed or the Claude tag page.