[FEATURE] Include full changelog content in GitHub release notes and Atom feeds

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement 🤔

Teams that manage Claude Code rollouts rely on Slack RSS integrations to stay on top of releases. Right now there are two Atom feed options, and neither gives a great experience in Slack:

1. CHANGELOG.md commit feed (github.com/anthropics/claude-code/commits/main/CHANGELOG.md.atom)

Every entry title is just chore: Update CHANGELOG.md and the <content> tag repeats that same commit message. There's no actual changelog content, so you get a Slack notification that says "chore: Update CHANGELOG.md" with zero detail about what changed.

2. Releases Atom feed (github.com/anthropics/claude-code/releases.atom)

This one does include the full "What's changed" bullet list in the <content> tag as HTML. It's better, but:

• Slack's RSS integration renders it as a single dense block or truncates it
• The release titles are just version numbers like v2.1.108 with no summary

The result is that AI enablement teams either manually check the docs changelog page or get near-useless "chore: Update CHANGELOG.md" pings in Slack.

(cc Slack thread with Will Steuk where he shared the CHANGELOG.md.atom workaround)

Proposed Solution 💡

A few options that would improve the feed experience:

Option A: Richer commit messages on CHANGELOG.md updates

Instead of the automated commit message chore: Update CHANGELOG.md, include the version number and a summary in the commit message. For example:

chore: Update CHANGELOG.md - v2.1.108 (24 changes)

Added: ENABLE_PROMPT_CACHING_1H env var, recap feature, slash command discovery via Skill tool
Improved: /model mid-conversation warnings, /resume picker, error messages
Fixed: paste in /login, diacritical marks, policy plugins, and 11 more

This would make the CHANGELOG.md.atom feed entries meaningful because the <content> tag in that feed mirrors the commit message.

Option B: Include a short summary in release titles

Instead of just v2.1.108, use something like v2.1.108 - 24 changes: prompt caching, recap, slash command discovery. The releases.atom feed uses the title directly, so Slack notifications would be much more informative at a glance.

Option C: Publish a dedicated RSS/Atom feed

Add a /feed.xml or /rss.xml endpoint to code.claude.com/docs/en/changelog that mirrors the page content. This is the gold standard for changelog discoverability and would also cover the blog at claude.com/blog (which has no feed either).

Any combination of these would be a big improvement. Option A is probably the lowest effort since it's just a CI workflow change.

Alternative Solutions 🔧

• What we're doing today: subscribed to the CHANGELOG.md.atom feed in a Slack channel, but every entry just says "chore: Update CHANGELOG.md" with a link. You have to click through to see what changed
• The releases.atom feed is slightly better but still not great in Slack's RSS rendering
• Manually checking the docs changelog page works but doesn't scale for teams tracking multiple tools

Priority

Medium - Would be very helpful

Feature Category

Documentation

Use Case Example 📋

1. Our AI enablement team at Slack manages Claude Code rollout for hundreds of engineers
2. We set up a Slack channel with an RSS feed for Claude Code changes so the team stays informed
3. A new release drops, Slack posts: chore: Update CHANGELOG.md
4. Nobody knows what changed without clicking through to GitHub
5. With this feature, the same Slack notification would show: v2.1.108 - Added prompt caching, recap feature, slash command discovery (or the full bullet list)
6. Engineers can quickly scan the channel and know whether an update is relevant to them

Additional Context 📸

What it looks like today in Slack:

Every notification is just "chore: Update CHANGELOG.md" with a commit link. No version number, no summary, no changelog content. The information exists in the CHANGELOG.md file and in the GitHub release body, it just doesn't make it into the feed entry that Slack displays.

The releases.atom feed is close but the <title> is just the version number (e.g., v2.1.109) and while the <content> has the full HTML changelog, Slack's RSS bot doesn't render it well for large releases.

For reference, the docs changelog at code.claude.com/docs/en/changelog has beautifully structured entries with version numbers, dates, and categorized bullet points (Added, Improved, Fixed, etc.). If even a fraction of that context made it into the Atom feeds, it would be a huge quality-of-life improvement for teams consuming these updates programmatically.

I'm sure other AI enablement teams at companies rolling out Claude Code would love a richer feed experience too 💡