Bump @sentry/react-native from 8.15.1 to 8.16.0

[dependabot]

Bumps @sentry/react-native from 8.15.1 to 8.16.0.

Release notes

Sourced from @​sentry/react-native's releases.

8.16.0

Features

• Capture errors that hit Expo Router's per-route ErrorBoundary (#6318)

  Wrap the boundary with Sentry.wrapExpoRouterErrorBoundary in your route file:

  // app/_layout.tsx
  import { ErrorBoundary as ExpoErrorBoundary } from 'expo-router';
  import * as Sentry from '@sentry/react-native';
  export const ErrorBoundary = Sentry.wrapExpoRouterErrorBoundary(ExpoErrorBoundary);

  Render-phase errors that reach the boundary are captured with route context (route.name, route.path, route.params), the in-flight navigation transaction is tagged as errored, and a breadcrumb is emitted. Concrete paths and params are gated behind sendDefaultPii.

Fixes

• Fix fatal NSInvalidArgumentException crash in RNSentryReplayBreadcrumbConverter when a touch breadcrumb path contains a non-dictionary element (#6346)
• Apply SENTRY_ENVIRONMENT, SENTRY_RELEASE and SENTRY_DIST build-time overrides to the JS bundled options to match the native SDKs (#6330)
• Fix user geo being dropped from the native scope by forwarding it as a structured object instead of a JSON string (#6309)
• Remove unused React/RCTTextView.h import that broke iOS builds on React Native 0.87, where the header was removed as part of the legacy architecture cleanup (#6322)

Internal

• Hide the dataCollection option until it is fully supported in React Native. It is exposed by @sentry/core but is not yet honored by the native SDKs (iOS/Android) nor by the RN-specific sendDefaultPii gates, so setting it would silently have no effect. Use sendDefaultPii instead. (#6345)

Dependencies

• Bump JavaScript SDK from v10.58.0 to v10.61.0 (#6321, #6332, #6349)
  • changelog
  • diff
• Bump Android SDK from v8.44.0 to v8.45.0 (#6323, #6344)
  • changelog
  • diff
• Bump Cocoa SDK from v9.18.0 to v9.19.0 (#6343)
  • changelog
  • diff

Changelog

Sourced from @​sentry/react-native's changelog.

8.16.0

Features

• Capture errors that hit Expo Router's per-route ErrorBoundary (#6318)

  Wrap the boundary with Sentry.wrapExpoRouterErrorBoundary in your route file:

  // app/_layout.tsx
  import { ErrorBoundary as ExpoErrorBoundary } from 'expo-router';
  import * as Sentry from '@sentry/react-native';
  export const ErrorBoundary = Sentry.wrapExpoRouterErrorBoundary(ExpoErrorBoundary);

  Render-phase errors that reach the boundary are captured with route context (route.name, route.path, route.params), the in-flight navigation transaction is tagged as errored, and a breadcrumb is emitted. Concrete paths and params are gated behind sendDefaultPii.

Fixes

• Fix fatal NSInvalidArgumentException crash in RNSentryReplayBreadcrumbConverter when a touch breadcrumb path contains a non-dictionary element (#6346)
• Apply SENTRY_ENVIRONMENT, SENTRY_RELEASE and SENTRY_DIST build-time overrides to the JS bundled options to match the native SDKs (#6330)
• Fix user geo being dropped from the native scope by forwarding it as a structured object instead of a JSON string (#6309)
• Remove unused React/RCTTextView.h import that broke iOS builds on React Native 0.87, where the header was removed as part of the legacy architecture cleanup (#6322)

Internal

• Hide the dataCollection option until it is fully supported in React Native. It is exposed by @sentry/core but is not yet honored by the native SDKs (iOS/Android) nor by the RN-specific sendDefaultPii gates, so setting it would silently have no effect. Use sendDefaultPii instead. (#6345)

Dependencies

• Bump JavaScript SDK from v10.58.0 to v10.61.0 (#6321, #6332, #6349)
  • changelog
  • diff
• Bump Android SDK from v8.44.0 to v8.45.0 (#6323, #6344)
  • changelog
  • diff
• Bump Cocoa SDK from v9.18.0 to v9.19.0 (#6343)
  • changelog
  • diff

Commits

• 7c15464 release: 8.16.0
• e763471 chore(e2e): Bump concurrent-ruby to 1.3.7 in samples and perf-tests (#6331)
• 3ba1463 fix(replay): Guard against non-dictionary touch breadcrumb path elements (#6346)
• 791b79b chore: update scripts/update-javascript.sh to 10.61.0 (#6349)
• 6f8ce25 chore: update scripts/update-sentry-android-gradle-plugin.sh to 6.13.0 (#6348)
• c79c2ae fix(core): Hide dataCollection option until supported in React Native (#6345)
• 6f79f71 feat(core): Capture Expo Router ErrorBoundary errors (#6318)
• 822d35b chore: update scripts/update-cocoa.sh to 9.19.0 (#6343)
• 2363c0f chore: update scripts/update-android.sh to 8.45.0 (#6344)
• ecf47a2 fix(core): Align SENTRY_ENVIRONMENT/RELEASE/DIST in JS bundled options with n...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coryzoon]

Handled in #858

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.