chore(deps): bump sentry/sentry-laravel from 3.8.2 to 4.3.0

[dependabot]

Bumps sentry/sentry-laravel from 3.8.2 to 4.3.0.

Release notes

Sourced from sentry/sentry-laravel's releases.

4.3.0

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

Features

• Add support for Laravel 11.0 [(#845)](getsentry/sentry-laravel#845)

  If you're upgrading an existing Laravel 10 application to the new Laravel 11 directory structure, you must change how Sentry integrates into the exception handler. Update your bootstrap/app.php with:

  <?php
  use Illuminate\Foundation\Application;
  use Illuminate\Foundation\Configuration\Exceptions;
  use Illuminate\Foundation\Configuration\Middleware;
  use Sentry\Laravel\Integration;
  return Application::configure(basePath: dirname(DIR))
  ->withRouting(
  web: DIR.'/../routes/web.php',
  commands: DIR.'/../routes/console.php',
  health: '/up',
  )
  ->withMiddleware(function (Middleware $middleware) {
  //
  })
  ->withExceptions(function (Exceptions $exceptions) {
  Integration::handles($exceptions);
  })->create();

  If you plan to perform up-time checks against the new Laravel 11 /up health URL, ignore this transaction in your config/sentry.php file, as not doing so could consume a substantial amount of your performance unit quota.

  // @see: https://docs.sentry.io/platforms/php/guides/laravel/configuration/options/#ignore-transactions
  'ignore_transactions' => [
      // Ignore Laravel's default health URL
      '/up',
  ],

Bug Fixes

• Set queue.publish spans as the parent of queue.process spans [(#850)](getsentry/sentry-laravel#850)

• Consider all http_* SDK options from the Laravel client in the test command [(#859)](getsentry/sentry-laravel#859)

4.2.0

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

... (truncated)

Changelog

Sourced from sentry/sentry-laravel's changelog.

4.3.0

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

Features

• Add support for Laravel 11.0 [(#845)](getsentry/sentry-laravel#845)

  If you're upgrading an existing Laravel 10 application to the new Laravel 11 directory structure, you must change how Sentry integrates into the exception handler. Update your bootstrap/app.php with:

  <?php
  use Illuminate\Foundation\Application;
  use Illuminate\Foundation\Configuration\Exceptions;
  use Illuminate\Foundation\Configuration\Middleware;
  use Sentry\Laravel\Integration;
  return Application::configure(basePath: dirname(DIR))
  ->withRouting(
  web: DIR.'/../routes/web.php',
  commands: DIR.'/../routes/console.php',
  health: '/up',
  )
  ->withMiddleware(function (Middleware $middleware) {
  //
  })
  ->withExceptions(function (Exceptions $exceptions) {
  Integration::handles($exceptions);
  })->create();

  If you plan to perform up-time checks against the new Laravel 11 /up health URL, ignore this transaction in your config/sentry.php file, as not doing so could consume a substantial amount of your performance unit quota.

  // @see: https://docs.sentry.io/platforms/php/guides/laravel/configuration/options/#ignore-transactions
  'ignore_transactions' => [
      // Ignore Laravel's default health URL
      '/up',
  ],

Bug Fixes

• Set queue.publish spans as the parent of queue.process spans [(#850)](getsentry/sentry-laravel#850)

• Consider all http_* SDK options from the Laravel client in the test command [(#859)](getsentry/sentry-laravel#859)

4.2.0

... (truncated)

Commits

• 7f88c20 release: 4.3.0
• 157aaa9 Prepare 4.3.0 (#860)
• 19e3da6 Add support for Laravel 11 (#845)
• 1b7fc23 Take all http_* options from the Laravel client in the test command (#859)
• 2c70e34 Make queue.publish spans the parent of queue.process spans (#850)
• 2529414 Merge branch 'release/4.2.0'
• 054638a release: 4.2.0
• 47bd677 Prepare 4.2.0 (#844)
• 678202f Bump PHP SDK to 4.5.0 (#843)
• 7b19858 Flush metrics when events are being flushed and after each request (#841)
• 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)

[dependabot]

The following labels could not be found: composer.

[github-actions]

I'm not approving this PR because it includes a major update of a dependency used in production

[github-actions]

I'm not approving this PR because it includes a major update of a dependency used in production

[github-actions]

I'm not approving this PR because it includes a major update of a dependency used in production

[dependabot]

Superseded by #1614.