docs: Add React Native SDK Turbo Module changelog entry

[alwx]

This PR adds a changelog entry for the Turbo Module instrumentation in the React Native SDK, versions 8.14.0 to 8.30.0. The entry covers native crash context, aggregated statistics, the Turbo Module data on spans, slow-call breadcrumbs, and the Old Architecture support (getsentry/sentry-react-native#6227, #6377, #6478, #6504, #6561, #6823).

The entry uses the react-native platform and the sdk_update broadcast category. The entry links to the TurboModule Context docs page (getsentry/sentry-docs#19949) for the setup and the options.

[vercel]

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

Project	Deployment	Actions	Updated
sentry-changelog	Ready	Preview	Oct 15, 2026 10:06am UTC

[cursor]

The plan checks successful loads of the new post URL. It also checks the detail-page failure rate, MDX compile errors, and list and RSS failure rates. An issue escalates when the detail-page failure rate rises or MDX errors appear.

Rollout complete

Services: sentry-changelog.

Plan

What changed

Public requests to /changelog/react-native-sdk-turbo-module-insights/ return the new Turbo Module post. The changelog list and the RSS feed include this post after the database sync. sentry-changelog must ship this change. The post is live after that ship and after the Sync Changelog job upserts the published slug. Production reads the database, not the Markdown file.

Risk

Malformed MDX in this entry fails the detail page for that slug. The list omits a bad summary and still shows other posts. A failed sync rolls back every file-based changelog upsert in that run. Users then keep a missing post and stale file-backed entries.

Intended effect

The change worked when production serves that slug with a successful span. Absent looks like a zero count for that URL after the ship. A zero count can also mean no visitor asked for the new slug.

Signal	Baseline	Rule	Source
Spans whose URL contains react-native-sdk-turbo-module-insights	0 spans in 2026-10-12T13:46:17Z to 2026-10-13T13:46:17Z	Confirmed when count rises above 0 and span.status is ok. Absent when count stays 0, or when spans exist only with span.status error.	Sentry org sentry project changelog environment:production url.full:*react-native-sdk-turbo-module-insights*

Regression watch

This Markdown can break MDX compile on the detail page, the list summaries, and the RSS feed. The detail-page failure rate already includes some missing-slug responses. If that rate rises, look at changelog_stage errors to separate a compile failure from 404 noise.

Signal	Baseline	Rule	Source
GET /changelog/[slug] failure rate	6.95% over 2026-10-12T13:46:17Z to 2026-10-13T13:46:17Z. 6.58% over 2026-10-06T13:46:17Z to 2026-10-13T13:46:17Z. Band 6.5-7.0%. Volume about 2.4 requests per minute in the 24h window.	Hold in the 6.5-7.0% band. Detected if the 24h rate rises above 7.0%. These values are window aggregates, not hourly buckets.	Sentry org sentry project changelog environment:production transaction:"GET /changelog/[slug]" with failure_rate()
changelog_stage:changelogDetailMdx errors	0 events in 2026-10-12T13:46:17Z to 2026-10-13T13:46:17Z	Detected if the count rises above 0.	Sentry org sentry project changelog environment:production changelog_stage:changelogDetailMdx
changelog_stage:getChangelogSummaries errors	0 events in 2026-10-12T13:46:17Z to 2026-10-13T13:46:17Z	Detected if the count rises above 0.	Sentry org sentry project changelog environment:production changelog_stage:getChangelogSummaries
GET /changelog failure rate	0% over 2026-10-12T13:46:17Z to 2026-10-13T13:46:17Z. About 11.9 requests per minute.	Hold at 0%. Detected if the rate rises above 0%.	Sentry org sentry project changelog environment:production transaction:"GET /changelog" with failure_rate()
GET /changelog/feed.xml failure rate	0% over 2026-10-12T13:46:17Z to 2026-10-13T13:46:17Z. About 1.6 requests per minute.	Hold at 0%. Detected if the rate rises above 0%.	Sentry org sentry project changelog environment:production transaction:"GET /changelog/feed.xml" with failure_rate()

Do not treat HTTPError: 403 on https://sentry.io/changelog/feed.xml as this change. That issue had 1 event in the 24h window.

Not observable

The Sync Changelog GitHub Action does not send Sentry events. Cache revalidation success is not in this project. The plan cannot confirm the rendered body text. Broadcast of this SDK update in the Sentry What's New panel is not in this project. Most GET /changelog/[slug] spans omit http.response.status_code, so 404 and 200 are not fully separable.

[antonis]

There is no docs.sentry.io page for turboModuleContextIntegration, so the entry links to the SDK changelog and the release pages.

Would it make sense to create the docs first so that we can keep the changelog short and reference the docs for detailed usage intructions?

[antonis]

Overall looks good. I'd advocate towards starting with the docs and updating the changelog accordingly. Most/all (at least recent ones) changelog entries link to the documentation.

[alwx]

@antonis I agree. I opened a docs PR for turboModuleContextIntegration: getsentry/sentry-docs#19949. When the docs PR is merged, I will make this entry shorter and link to the docs page for the setup and the options.

[alwx]

The docs PR was merged!

[antonis]

@alwx should we update this to point to the doc https://docs.sentry.io/platforms/react-native/integrations/turbo-module-context/ ?

[alwx]

@antonis done! The entry now links to the TurboModule Context docs page, and I removed the detailed sections that the docs page now covers.

[antonis]

LGTM

[cursor]

Verified in production

• The new Turbo Module post loaded successfully and changelog pages stayed healthy.