Skip to content

publish: getsentry/sentry-react-native@8.3.0 #7350

Closed

Description

@sentry-release-bot

Requested by: @alwx

Merge target: (default)

Quick links:

Assign the accepted label to this issue to approve the release.

Targets

  • npm
  • github
  • registry

Checked targets will be skipped (either already published or user-requested skip). Uncheck to retry a target.


📋 Changelog

Features

  • Add onNativeLog callback to intercept and forward native SDK logs to JavaScript console (#5622)
    • The callback receives native log events with level, component, and message properties
    • Only works when debug: true is enabled in Sentry.init
    • Use consoleSandbox inside the callback to prevent feedback loops with Sentry's console integration
      import * as Sentry from '@sentry/react-native';
      
      Sentry.init({
        debug: true,
        onNativeLog: ({ level, component, message }) => {
          // Use consoleSandbox to avoid feedback loops
          Sentry.consoleSandbox(() => {
            console.log(
              `[Sentry Native] [${level.toUpperCase()}] [${component}] ${message}`
            );
          });
        }
      });
  • Add expo constants on event context (#5748)
  • Capture dynamic route params as span attributes for Expo Router navigations (#5750)
  • EAS Build Hooks (#5666)
    • Capture EAS build events in Sentry. Add the following to your package.json:
      {
        "scripts": {
          "eas-build-on-complete": "sentry-eas-build-on-complete"
        }
      }
      Set SENTRY_DSN in your EAS secrets, and optionally SENTRY_EAS_BUILD_CAPTURE_SUCCESS=true to also capture successful builds.

Fixes

  • App start data not attached to sampled transactions when preceded by unsampled transactions (#5756)
  • Resolve relative SOURCEMAP_FILE paths against the project root in the Xcode build script (#5730)
  • Fixes the issue with unit mismatch in adjustTransactionDuration (#5740)
  • Handle inactive state for spans (#5742)

Dependencies

Activity

  1. github-actions commented on Mar 5, 2026

    @github-actions

    Publishing: run#22717090889

  2. github-actions commented on Mar 5, 2026

    @github-actions

    Failed to publish. (run logs)

    Bad branch? You can delete with ease and start over.

  3. github-actions commented on Mar 5, 2026

    @github-actions

    Publishing: run#22717090889

  4. github-actions commented on Mar 5, 2026

    @github-actions

    Publishing: run#22718331348

  5. github-actions commented on Mar 5, 2026

    @github-actions

    Failed to publish. (run logs)

    Bad branch? You can delete with ease and start over.

  6. github-actions commented on Mar 5, 2026

    @github-actions

    Published successfully: run#22718331348

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions