build: Bump sentry/sentry-laravel from 3.8.2 to 4.0.0

[dependabot]

Bumps sentry/sentry-laravel from 3.8.2 to 4.0.0.

Release notes

Sourced from sentry/sentry-laravel's releases.

4.0.0

The Sentry SDK team is thrilled to announce the immediate availability of Sentry Laravel SDK v4.0.0.

Breaking Change

This version adds support for the underlying Sentry PHP SDK v4.0. Please refer to the PHP SDK sentry-php/UPGRADE-4.0.md guide for a complete list of breaking changes.

• This version exclusively uses the envelope endpoint to send event data to Sentry.

  If you are using sentry.io, no action is needed. If you are using an on-premise/self-hosted installation of Sentry, the minimum requirement is now version >= v20.6.0.

• You need to have ext-curl installed to use the SDK.

• The IgnoreErrorsIntegration integration was removed. Use the ignore_exceptions option instead.

  // config/sentry.php
  'ignore_exceptions' => [BadThingsHappenedException::class],

  This option performs an is_a check now, so you can also ignore more generic exceptions.

Features

• Enable distributed tracing for outgoing HTTP client requests [(#797)](getsentry/sentry-laravel#797)

  This feature is only available on Laravel >= 10.14. When making a request using the Laravel Http facade, we automatically attach the sentry-trace and baggage headers.

  This behaviour can be controlled by setting trace_propagation_targets in your config/sentry.php file.

  // config/sentry.php
  // All requests will contain the tracing headers. This is the default behaviour.
  'trace_propagation_targets' => null,
  // To turn this feature off completely, set the option to an empty array.
  'trace_propagation_targets' => [],
  // To only attach these headers to some requests, you can allow-list certain hosts.
  'trace_propagation_targets' => [
  'examlpe.com',
  'api.examlpe.com',
  ],

... (truncated)

Changelog

Sourced from sentry/sentry-laravel's changelog.

4.0.0

The Sentry SDK team is thrilled to announce the immediate availability of Sentry Laravel SDK v4.0.0.

Breaking Change

This version adds support for the underlying Sentry PHP SDK v4.0. Please refer to the PHP SDK sentry-php/UPGRADE-4.0.md guide for a complete list of breaking changes.

• This version exclusively uses the envelope endpoint to send event data to Sentry.

  If you are using sentry.io, no action is needed. If you are using an on-premise/self-hosted installation of Sentry, the minimum requirement is now version >= v20.6.0.

• You need to have ext-curl installed to use the SDK.

• The IgnoreErrorsIntegration integration was removed. Use the ignore_exceptions option instead.

  // config/sentry.php
  'ignore_exceptions' => [BadThingsHappenedException::class],

  This option performs an is_a check now, so you can also ignore more generic exceptions.

Features

• Enable distributed tracing for outgoing HTTP client requests [(#797)](getsentry/sentry-laravel#797)

  This feature is only available on Laravel >= 10.14. When making a request using the Laravel Http facade, we automatically attach the sentry-trace and baggage headers.

  This behaviour can be controlled by setting trace_propagation_targets in your config/sentry.php file.

  // config/sentry.php
  // All requests will contain the tracing headers. This is the default behaviour.
  'trace_propagation_targets' => null,
  // To turn this feature off completely, set the option to an empty array.
  'trace_propagation_targets' => [],
  // To only attach these headers to some requests, you can allow-list certain hosts.
  'trace_propagation_targets' => [
  'examlpe.com',
  'api.examlpe.com',
  ],

... (truncated)

Commits

• b6fbabb release: 4.0.0
• 48c7977 Merge pull request #800 from getsentry/4.x
• a19357e Prepare 4.0 (#796)
• 229287c Add support for Livewire 3 (#798)
• f132ad5 Refactor HTTP client integration feature (#797)
• 9f3a0d7 Improve how we signal that a route was matched (#772)
• a36f34b Some cleanup (#795)
• d1b6d76 Add support for PHPUnit 10 (#794)
• 90fd313 Bump PHP SDK to 4.0 (#793)
• 9624a88 Add permissions to GitHub actions (#791)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)