Test with sentry-wizard v8.0.0 (new major) for breaking changes

[antonis]

Summary

sentry-wizard v8.0.0 is a new major release. We should test the React Native wizard flow against it and check for any breaking changes before recommending / bundling it for our users.

Context

The main breaking change in v8.0.0 is that the wizard now installs the JS SDK at ^11 for a number of framework integrations (Angular, Cloudflare, Next.js, Nuxt, React Router, Remix, SvelteKit). React Native is not in that list.

Important

Our plan is to bump to Sentry JS 11 in our next major — not now. So this issue is about verifying the new wizard major doesn't break the current React Native setup flow while we remain on JS 10, not about adopting the JS 11 requirement yet.

Tasks

• Run the react-native wizard flow with @sentry/wizard@8 end-to-end and confirm it completes without errors.
• Verify the wizard still installs / configures a JS-10-compatible @sentry/react-native (does not force @sentry/*@^11 or an incompatible peer).
• Check the Node.js support / version warnings introduced for SDK v11 don't spuriously fire or block the RN flow.
• Diff the generated config (metro, sentry.properties, native project changes) against the current wizard output for regressions.
• Note any changes we'll need to coordinate when we do move to JS 11 in the next major.

References

• Release notes: https://github.com/getsentry/sentry-wizard/releases/tag/v8.0.0

[linear-code]

RN-794

[antonis]

Verified @sentry/wizard@8.0.0 against the RN flow — two ways: a source diff of the published v7.0.3 vs v8.0.0 packages, and a live run of npx @sentry/wizard@8.0.0 -i reactNative against a throwaway RN project (RN 0.76.5, Node 22.19).

TL;DR: v8.0.0 is safe for the React Native flow while we stay on JS 10.

Task	Result
Flow completes without errors	✅ Live run started clean (welcome → git check → RN detection → install). The entire dist/src/react-native/ tree is byte-identical to v7.0.3.
Installs a JS-10-compatible SDK, no @sentry/*@^11	✅ RN step installs bare @sentry/react-native (no version pin). Live install wrote @sentry/react-native@^8.27.0 and resolved @sentry/core / react / browser @ 10.75.0; zero packages on v11.
Node-version warning (wizard #1354) doesn't spuriously fire	✅ warnIfNodeVersionUnsupportedBySdkV11 is wired only into the 7 JS-framework wizards, not the RN path. No such text in the live log.
New dataCollection prompt (wizard #1358/#1359) doesn't leak into RN	✅ Referenced only in the JS wizards; absent from the RN path and the live log.
Diff generated config for regressions	✅ metro.js, gradle.js, xcode.js, cocoapod.js, javascript.js, options.js all byte-identical v7→v8. Only shared change reaching common code is a new printSdkV11MigrationGuideIfOutdated, keyed to the 7 JS packages — not @sentry/react-native — and not called from the RN flow.

Next-major (JS 11) coordination: when RN moves to JS 11, the wizard won't surface an RN-specific migration link (@sentry/react-native isn't in its slug map). Tracked in #6776.

Note on scope: the live run is validated up to the Sentry login / project-selection step — the full end-to-end (auth + native file patching) needs interactive Sentry auth this environment can't provide. The config-generation code past that point is covered by the byte-identical source diff rather than executed.

The version bump itself is #6775.