Sourced from sentry/sentry-laravel's releases.

4.15.0

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)](getsentry/sentry-laravel#1000)

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

  'channels' => [
      ...
      'sentry' => [
          '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::driver('sentry')->info('User {id} failed to login.', ['id' => $user->id]);
  

4.14.1

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)](getsentry/sentry-laravel#1002)

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

Sourced from sentry/sentry-laravel's changelog.

4.15.0

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)](getsentry/sentry-laravel#1000)

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

  'channels' => [
      ...
      'sentry' => [
          '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 use Illuminate\Support\Facades\Log;
  Log::driver('sentry')->info('User {id} failed to login.', ['id' => $user->id]);
  

4.14.1

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)](getsentry/sentry-laravel#1002)

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

• 481398f release: 4.15.0
• 5212efa Prepare 4.15.0 (#1005)
• a47c482 Expose enable_logs option (#1004)
• f33d9ff Add Sentry logs (#1000)
• 7dda008 Merge branch 'release/4.14.1'
• 8b71a92 release: 4.14.1
• ad14f48 Prepare 4.14.1 (#1003)
• 93247f9 Ensure there is a newline before writing env variables (#1002)
• 42d03af Merge branch 'release/4.14.0'
• See full diff in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions