Skip to content

Releases: getsentry/sentry-laravel

4.17.0

15 Oct 10:07

Choose a tag to compare

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

Features

  • Auto configure Sentry log channels. (#1042)

Configuring the channel is no longer required. To enable logs for Sentry, the following environment variables
need to be configured:

LOG_CHANNEL=stack
LOG_STACK=single,sentry_logs
SENTRY_ENABLE_LOGS=true

Sentry will use LOG_LEVEL to determine the minimum log level, but it's possible to overwrite it just for Sentry
using SENTRY_LOG_LEVEL.

LOG_LEVEL=info
SENTRY_LOG_LEVEL=warning

Misc

  • Add sentry.origin attribute to LogsHandler. (#1041)

4.16.0

10 Sep 16:41

Choose a tag to compare

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

Features

4.15.3

04 Sep 14:39

Choose a tag to compare

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

Bug Fixes

  • Guard against empty cache event keys (#1031)

4.15.2

04 Sep 12:23

Choose a tag to compare

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

Bug Fixes

  • Replace the session key in cache span names by a placeholder (#1009)

Misc

  • Bump the PHP SDK to version 4.15.2 (#1028)

4.15.1

24 Jun 12:53

Choose a tag to compare

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

Misc

  • Bump the PHP SDK to version 4.14.1 (#1013)

4.15.0

12 Jun 20:58

Choose a tag to compare

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

Features

  • Add support for Sentry Structured Logs (#1000)

    To enable this feature, add the sentry_logs log channel in your config/logging.php configuration:

    'channels' => [
        ...
        'sentry_logs' => [
            'driver' => 'sentry_logs',
            'level' => env('LOG_LEVEL', 'info'),
        ],
        ...
    ],

    Add SENTRY_ENABLE_LOGS=true to your .env file.

    Use the Log facade to sent your logs to Sentry. To learn more, head over to the Laravel docs.

    use Illuminate\Support\Facades\Log;
    
    Log::channel('sentry_logs')->info('User {id} failed to login.', ['id' => $user->id]);

    To learn more, head over to our docs.

4.14.1

07 Jun 07:54

Choose a tag to compare

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

Bug Fixes

  • Ensure there is a newline before writing env variables (#1002)

    Fixed an issue where the php artisan sentry:publish command might not properly add newlines when writing environment variables to the .env file.

4.14.0

02 Jun 10:05

Choose a tag to compare

Bug Fixes

  • Fix tracing when using Laravel Octane (#997)

    When using Laravel Octane, the SDK now correctly cleans up it's state after each request, ensuring that traces are correctly reported.

Misc

  • Add sentry prefix to publish group name (#992)

    When running php artisan vendor:publish, the Sentry package exports are now prefixed with sentry, making it easier to distinguish from other packages.

  • Remove support for traceparent header (#994)

    The W3C's traceparent header is no longer automatically picked up and emitted by the SDK to prevent non-Sentry SDKs from starting a trace that is unwanted.

4.13.0

18 Feb 10:33

Choose a tag to compare

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

Features

  • Add support for Laravel 12.0 (#980)

4.12.0

05 Feb 13:15

Choose a tag to compare

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

Features

  • Improve generation of slug for scheduled job cron monitoring (#977)

    For scheduled jobs it's no longer needed to manually provide a slug to the ->sentryMonitor() call, it will be derived from the job class name.

Bug Fixes

  • Fix unable to parse notifiable (#974)
  • Fix triggering a missing attribute violation (#978)

Misc

  • Disable scheduled task tracing for backgrounded tasks (#975)

    Backgrounded tasks show up a ~1ms transactions right now because we are effectively monitoring the time it takes to start the background process instead of the execution.
    We are working on a solution to this problem, but in the meantime, we are disabling the monitoring of backgrounded tasks (that was introduces in 4.11.0).