4.10.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.10.1.

Bug Fixes

• Fixed a PHP 8.4 deprecation notice (#954)

4.10.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.10.0.

Features

• The SDK was updated to support PHP 8.4 (#952)

Misc

• The SDK does no longer emit Metrics. All public Metrics APIs are now no-op, internal APIs were removed (#951)

4.9.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.9.0.

Misc

• Allow the cache store used by the console scheduling integration to be overridden (#942)

• Set http breadcrumb levels based on response code (#940)

4.8.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.8.0.

Bug Fixes

• Fix php artisan sentry:publish mangling the .env file (#928)

• Fix not (correctly) reporting transactions when using Laravel Octane (#936)

Misc

• Improve the stacktrace of the php artisan sentry:test event (#926)

• Remove outdated JS SDK installation step from php artisan sentry:publish (#930)

4.7.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.7.1.

Bug Fixes

• Always remove the XSRF-TOKEN cookie value before sending to Sentry (#920)
• Fix trace durations when using Octane (#921)
• Handle clousre route names (#921)
• Don't rely on facades when accessing the Laravel context (#922)
• Normalize array of cache key names before converting to string (#923)

4.7.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.7.0.

Features

• Add support for Cache Insights Module (#914). To learn more about this module, visit https://docs.sentry.io/product/insights/caches/. This feature requires Laravel v11.11.0 or higher.

  Cache tracing is enabled by default for new SDK installations. To enable this feature in your existing installation, update your config/sentry.php file with 'cache' => env('SENTRY_TRACE_CACHE_ENABLED', true), under 'tracing'.

4.6.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.6.1.

Bug Fixes

• Fix wrong queue grouping in the queue Insights Module (#910)

4.6.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v4.6.0.

Features

• Add support for the Queue Insights Module (#902). To learn more about this module, visit https://docs.sentry.io/product/performance/queue-monitoring/.

  Queue tracing is enabled by default for new SDK installations. To enable this feature in your existing installation, update your config/sentry.php file with 'queue_jobs' => env('SENTRY_TRACE_QUEUE_JOBS_ENABLED', true), or set SENTRY_TRACE_QUEUE_JOBS_ENABLED=true in your environment (#903).

Bug Fixes

• Check if a span is sampled before creating child spans (#898)

• Always register the console sentryMonitor() macro. This fixes the macro not being available when using Laravel Lumen (#900)

• Avoid manipulating the config when resolving disks (#901)

Misc

• Various Spotlight improvements, such as the addition of a new SENTRY_SPOTLIGHT environment variable and not requiring a DSN to be set to use Spotlight (#892)

4.5.1

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

Bug Fixes

• Fix discarded attribute violation reporter not accepting multiple property names (#890)

4.5.0

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

Features

• Limit when SQL query origins are being captured (#881)

  We now only capture the origin of a SQL query when the query is slower than 100ms, configurable by the SENTRY_TRACE_SQL_ORIGIN_THRESHOLD_MS environment variable.

• Add tracing and breadcrumbs for Notifications (#852)

• Add reporter for Model::preventAccessingMissingAttributes() (#824)

• Make it easier to enable the debug logger (#880)

  You can now enable the debug logger by adding the following to your config/sentry.php file:

  'logger' => Sentry\Logger\DebugFileLogger::class, // This will log SDK logs to `storage_path('logs/sentry.log')`

  Only use this in development and testing environments, as it can generate a lot of logs.

Bug Fixes

• Fix Lighthouse operation not detected when query contained a fragment before the operation (#883)

• Fix an exception being thrown when the username extracted from the authenticated user model is not a string (#887)