Skip to content

chore(docs): Group version support and all-SDK changes in the v11 migration guide - #24423

Closed
chargome wants to merge 1 commit into
docs/v11-migration-1-fixesfrom
docs/v11-migration-2-all-sdks
Closed

chargome wants to merge 1 commit into
docs/v11-migration-1-fixesfrom
docs/v11-migration-2-all-sdks

Conversation

@chargome

@chargome chargome commented Sep 16, 2026

Copy link
Copy Markdown
Member

We had feedback that the v11 guide is too long. The root problem is that it is sorted by kind of change (Behaviour / Removed / Renames / Types), so a single SDK shows up in three places and readers cannot tell which parts apply to them. This stack re-sorts it by who is affected.

This part adds "Changes for all SDKs" and compresses the version-support section into a list. Duplicates collapse here: the logs and metrics options become one section, the package removals one list, and the integration renames one table.

Intermediate state: a few in-page links point at headings that arrive later in the stack. They all resolve by part 7.

Part 2 of 7.

🤖 Generated with Claude Code

… guide

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@chargome
chargome added this pull request to stack #24429 September 16, 2026 08:38
@chargome chargome changed the title docs(migration): Group version support and all-SDK changes in the v11 guide chore(docs): Group version support and all-SDK changes in the v11 migration guide Sep 16, 2026
@chargome chargome self-assigned this Sep 16, 2026
@chargome

Copy link
Copy Markdown
Member Author

Superseded by #24430, which contains this same change as a single PR.

@chargome chargome closed this Sep 16, 2026
@chargome
chargome deleted the docs/v11-migration-2-all-sdks branch September 16, 2026 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant