3.5.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.5.1.

Bug Fixes

• Prevent registering terminating callback multiple times and guard against finishing already finished transactions (#717)

  This fixes the Call to a member function finish() on null that could occur when using long running processes like on the CLI or with Laravel Octane.

3.5.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.5.0.

Features

• Improve terminating callbacks visibility (#707)

  This adds support for performance traces that happen after the terminable middleware emits the response.

• Add http.route.response span (#708)

  Note: This feature requires Laravel >= 10.13.0 to hail any new spans.

  This will add a http.route.response span which identifies possible actions taken to prepare the response, especially when using Illuminate\Contracts\Support\Responsable classes.

Bug Fixes

• Refactor queue integration (#692)

  This improves and fixes some edge cases around scope management when running Laravel Queues.

• Improve lazyLoadingViolationReporter helper (#709)

  Check for $model->exists and $model->wasRecentlyCreated before capturing the event.

Misc

• Bump the underlying PHP SDK to version ^3.19 to enforce an upgrade to fix an issue in libcurl >= v8.1.0 (#711)

3.4.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.4.1.

Bug Fixes

• Fix missing sentryMonitor macro if no DSN is set (#698)

3.4.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.4.0.

Features

• Add helper to report lazy loading violations (#678)

  We've added a new helper that makes reporting lazy loading violation to Sentry in production very easy:

  // See: https://laravel.com/docs/10.x/eloquent-relationships#preventing-lazy-loading
  \Illuminate\Database\Eloquent\Model::preventLazyLoading();
  
  // In production we just report the lazy loading violation instead of crashing the application since it's a performance issue not a security issue
  if (app()->isProduction()) {
    \Illuminate\Database\Eloquent\Model::handleLazyLoadingViolationUsing(
      \Sentry\Laravel\Integration::lazyLoadingViolationReporter(),
    );
  }

  We let you know which model and relation caused the lazy loading violation and we also include the origin of the violation so you can find the culprit quickly.

• Reintroduce Laravel Lumen support (#685)

  We dropped support for Laravel Lumen (10.x) in v3.0.0, but we are happy to announce that it is back!

3.3.3

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.3.3.

Bug Fixes

• Fix CheckIn constructor argument order (#680)
• Fix missing breadcrumbs for jobs throwing an exception (#633)

3.3.2

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.3.2.

Bug Fixes

• Fix "Object of class Closure could not be converted to string" error when tracing redis_commands (#668)

3.3.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.3.1.

Bug Fixes

• Fix scheduled commands running in the background not reporting success/failure (#664)

3.3.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.3.0.
This release adds initial support for Cron Monitoring as well as new performance spans and breadcrumbs.

Warning
Cron Monitoring is currently in beta. Beta features are still in-progress and may have bugs. We recognize the irony.
If you have any questions or feedback, please email us at crons-feedback@sentry.io, reach out via Discord (#cronjobs), or open an issue.

Features

• Add inital support for Cron Monitoring (#659)

  After creating your Cron Monitor on https://sentry.io, you can add the sentryMonitor() macro to your scheduled tasks defined in your app/Console/Kernel.php file.
  This will let Sentry know if your scheduled task started, whether the task was successful or failed, and its duration.

  protected function schedule(Schedule $schedule)
  {
      $schedule->command('emails:send')
          ->everyHour()
          ->sentryMonitor('<your-monitor-slug>'); // add this line
  }

• Add Livewire tracing integration (#657)

  You can enable this feature by adding new config options to your config/sentry.php file.

  'breadcrumbs' => [
      // Capture Livewire components in breadcrumbs
      'livewire' => true,
  ],
  'tracing' => [
      // Capture Livewire components as spans
      'livewire' => true,
  ],

• Add Redis operation spans & cache event breadcrumbs (#656)

  You can enable this feature by adding new config options to your config/sentry.php file.

  'breadcrumbs' => [
      // Capture Laravel cache events in breadcrumbs
      'cache' => true,
  ],
  'tracing' => [
      // Capture Redis operations as spans (this enables Redis events in Laravel)
      'redis_commands' => env('SENTRY_TRACE_REDIS_COMMANDS', false),
  
      // Try to find out where the Redis command originated from and add it to the command spans
      'redis_origin' => true,
  ],

• Add HTTP client request breadcrumbs (#640)

  You can enable this feature by adding a new config option to your config/sentry.php file.

  'breadcrumbs' => [
      // Capture HTTP client requests information in breadcrumbs
      'http_client_requests' => true,
  ],

• Offer the installation of a JavaScript SDK when running sentry:publish (#647)

Bug Fixes

• Fix a log channel context crash when unexpected values are passed (#651)

Misc

• The SDK is now licensed under MIT (#654)
  • Read more about Sentry's licensing here.

3.2.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.2.0.
This release adds support for Laravel 10.

Features

• Add support for Laravel 10 (#630)
  • Thanks to @jnoordsij for their contribution.
• Add tracing.http_client_requests option (#641)

  • You can now disable HTTP client tracing in your config/sentry.php file

    'tracing' => [
        'http_client_requests' => true|false, // This feature is enabled by default
    ],

3.1.3

• Increase debug trace limit count to 20 in Integration::makeAnEducatedGuessIfTheExceptionMaybeWasHandled() (#622)
  • Look futher into the backtrace to check if report() was called.
• Run the testsuite against PHP 8.2 (#624)