Skip to content

docs(sdk): Migrate client-reports spec to new format#16516

Merged
stephanie-anderson merged 4 commits intomasterfrom
docs/migrate-client-reports-spec-format
Feb 23, 2026
Merged

docs(sdk): Migrate client-reports spec to new format#16516
stephanie-anderson merged 4 commits intomasterfrom
docs/migrate-client-reports-spec-format

Conversation

@stephanie-anderson
Copy link
Contributor

@stephanie-anderson stephanie-anderson commented Feb 23, 2026

Migrate sdk/telemetry/client-reports.mdx to the new spec format established in #16461.

  • Add versioned frontmatter with 22-entry changelog derived from full git history
  • Restructure into standard spec sections with SpecRfcAlert, SpecMeta, SpecSection, SpecChangelog components
  • Consolidate network failure recording rules from expected-features/index.mdx into the client-reports spec as the single source of truth
  • Remove client report section from envelope-items.mdx (content now lives in client-reports wire format section)
  • Split network failure recording into per-status-code SpecSections with precise since versions
  • Add wire format section with payload tables including Since columns
  • Replace inline rules in expected-features with references to the client-reports spec

Co-Authored-By: Claude noreply@anthropic.com

Add versioned frontmatter with 22-entry changelog derived from git
history. Restructure content into standard spec sections (SpecRfcAlert,
SpecMeta, SpecSection, SpecChangelog). Consolidate network failure
recording rules from expected-features and envelope item constraints
from envelope-items into the client-reports spec as the single source
of truth.

- Split network failure recording into per-status-code SpecSections
- Add wire format section with payload tables and Since columns
- Replace inline rules in expected-features with spec references
- Remove client report section from envelope-items

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Feb 23, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
develop-docs Ready Ready Preview, Comment Feb 23, 2026 1:41pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
sentry-docs Ignored Ignored Preview Feb 23, 2026 1:41pm

Request Review

@stephanie-anderson stephanie-anderson enabled auto-merge (squash) February 23, 2026 13:26
stephanie-anderson and others added 2 commits February 23, 2026 14:34
The previous wording "except for HTTP 429 and HTTP 413" could be
misread as those codes not requiring a client report. Reword to
make it clear they have dedicated sections with additional requirements.

Co-Authored-By: Claude <noreply@anthropic.com>
@stephanie-anderson stephanie-anderson merged commit 378d844 into master Feb 23, 2026
15 checks passed
@stephanie-anderson stephanie-anderson deleted the docs/migrate-client-reports-spec-format branch February 23, 2026 13:42
@github-actions github-actions bot locked and limited conversation to collaborators Mar 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

sdk-develop-docs PRs touching develop-docs/sdk

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants