[antonis]

📢 Type of change

• Enhancement

📜 Description

Follow-up to #6794. sentryWebViewProps is a helper rather than an integration, so it was invisible to Sentry's feature-adoption telemetry (it never appears in event.sdk.integrations).

This registers a no-op WebViewTracePropagation marker (via the existing registerFeatureMarker util) when sentryWebViewProps is called, so the feature flows through to event.sdk.integrations — the channel Sentry uses to measure feature adoption across SDKs. Same approach already used by GlobalErrorBoundary, NavigationContainer, and MobileReplay.

• Marker registered on use (not on injection success), so it reflects that the app wired up the feature even when there is no active trace to inject.
• Idempotent and fails quietly — a second call is a no-op, and it never breaks rendering (no-op when the SDK is disabled / no client).
• Internal constant only (WEBVIEW_INTEGRATION_NAME); no public API change (api-report unchanged).

💡 Motivation and Context

Without a marker we can't measure how many apps enable WebView trace propagation. The feature is a plain helper, so it needs an explicit adoption signal.

This is the React Native half of a cross-SDK effort — matching issues are filed for the native SDKs with the aligned marker name WebViewTracePropagation:

• Apple: COCOA-2097
• Android: JAVA-796
• Flutter: DART-483

💚 How did you test it?

Unit tests in packages/core/test/tracing/webview.test.ts (4 new): registers on use; registers even with no active trace; idempotent; no-throw when no client. Local: 66/66 tests pass, webview.ts 100% covered, build green, api-report unchanged, oxlint/oxfmt/side-effects/circular-dep all pass.

📝 Checklist

• I added tests to verify changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• I updated the docs if needed.
• I updated the wizard if needed.
• All tests passing.
• Public API changes reviewed by another Mobile SDK team member or implemented according to the develop docs spec.
• No breaking changes.

🔮 Next steps

Mirror the adoption marker on the native SDKs (COCOA-2097, JAVA-796, DART-483) with the same WebViewTracePropagation name.

🤖 Generated with Claude Code

[github-actions]

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

• feat(tracing): Track WebView trace-propagation feature adoption by antonis in #6938

• chore(deps): update Wizard to v9.0.0 by github-actions in #6936
• chore(deps): update CLI to v3.8.2 by github-actions in #6933
• ci: Move CI off end-of-life Node versions to Node 22 by antonis in #6927

---

_{🤖 This preview updates automatically when you update the PR.}

[linear-code]

COCOA-2097

JAVA-796

DART-483

[github-actions]

	Fails
🚫	Pull request is not ready for merge, please add the "ready-to-merge" label to the pull request

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 8951080