Bump sentry/sentry-laravel from 3.0.0 to 3.2.0

[dependabot[bot]]

Bumps sentry/sentry-laravel from 3.0.0 to 3.2.0.

Release notes

Sourced from sentry/sentry-laravel's releases.

3.2.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.2.0. This release adds support for Laravel 10.

Features

• Add support for Laravel 10 [(#630)](getsentry/sentry-laravel#630)
  • Thanks to @​jnoordsij for their contribution.
• Add tracing.http_client_requests option [(#641)](getsentry/sentry-laravel#641)

  • You can now disable HTTP client tracing in your config/sentry.php file

    'tracing' => [
        'http_client_requests' => true|false, // This feature is enabled by default
    ],
    

3.1.3

• Increase debug trace limit count to 20 in Integration::makeAnEducatedGuessIfTheExceptionMaybeWasHandled() (#622)
  • Look futher into the backtrace to check if report() was called.
• Run the testsuite against PHP 8.2 (#624)

3.1.2

• Set traces_sample_rate to null by default (#616)

  • Make sure to update your config/sentry.php.

    Replace

    'traces_sample_rate' => (float)(env('SENTRY_TRACES_SAMPLE_RATE', 0.0)),
    

    with

    'traces_sample_rate' => env('SENTRY_TRACES_SAMPLE_RATE') === null ? null : (float)env('SENTRY_TRACES_SAMPLE_RATE'),
    

• Fix exceptions sent via the report() helper being marked as unhandled (#617)

3.1.1

• Fix missing scope information on unhandled exceptions (#611)

3.1.0

• Unhandled exceptions are now correctly marked as handled: false and displayed as such on the issues list and detail page (#608)
  • Make sure to update your App/Exceptions/Handler.php file to enable this new behaviour. See https://docs.sentry.io/platforms/php/guides/laravel/

3.0.1

• Remove incorrect checks if performance tracing should be enabled and rely on the transaction sampling decision instead (#600)
• Fix SENTRY_RELEASE .env variable not working when using config caching (#603)

Changelog

Sourced from sentry/sentry-laravel's changelog.

3.2.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.2.0. This release adds support for Laravel 10.

Features

• Add support for Laravel 10 [(#630)](getsentry/sentry-laravel#630)
  • Thanks to @​jnoordsij for their contribution.
• Add tracing.http_client_requests option [(#641)](getsentry/sentry-laravel#641)

  • You can now disable HTTP client tracing in your config/sentry.php file

    'tracing' => [
        'http_client_requests' => true|false, // This feature is enabled by default
    ],
    

3.1.3

• Increase debug trace limit count to 20 in Integration::makeAnEducatedGuessIfTheExceptionMaybeWasHandled() (#622)
  • Look futher into the backtrace to check if report() was called.
• Run the testsuite against PHP 8.2 (#624)

3.1.2

• Set traces_sample_rate to null by default (#616)

  • Make sure to update your config/sentry.php.

    Replace

    'traces_sample_rate' => (float)(env('SENTRY_TRACES_SAMPLE_RATE', 0.0)),
    

    with

    'traces_sample_rate' => env('SENTRY_TRACES_SAMPLE_RATE') === null ? null : (float)env('SENTRY_TRACES_SAMPLE_RATE'),
    

• Fix exceptions sent via the report() helper being marked as unhandled (#617)

3.1.1

• Fix missing scope information on unhandled exceptions (#611)

3.1.0

• Unhandled exceptions are now correctly marked as handled: false and displayed as such on the issues list and detail page (#608)
  • Make sure to update your App/Exceptions/Handler.php file to enable this new behaviour. See https://docs.sentry.io/platforms/php/guides/laravel/

3.0.1

... (truncated)

Commits

• 55ad9bd release: 3.2.0
• ca6a451 Prepare 3.2.0 (#642)
• 4be4c18 Update README.md for Laravel 10 (#638)
• d64cf29 ref: Add tracing.http_client_requests option (#641)
• eb6eec1 Add Laravel 10 support (#630)
• 18c8ca5 Merge branch 'release/3.1.3'
• 392efc8 release: 3.1.3
• 338050e Prepare 3.1.3 (#631)
• 1f1493d ref: Bump CI to PHP 8.2 (#624)
• bffd417 Change debug trace limit count (#622)
• 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 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[bot]]

Superseded by #151.