Bump sentry/sentry-laravel from 3.4.0 to 3.7.0

[dependabot[bot]]

Bumps sentry/sentry-laravel from 3.4.0 to 3.7.0.

Release notes

Sourced from sentry/sentry-laravel's releases.

3.7.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.7.0.

Features

• Tracing without Performance [(#719)](getsentry/sentry-laravel#719)

  The SDK will now continue a trace from incoming HTTP requests, even if performance is not enabled. To continue a trace outward, you may attach the Sentry tracing headers to any HTTP client request. You can fetch the required header values by calling \Sentry\getBaggage() and \Sentry\getTraceparent().

• Add performance traces and breadcrumbs for filesystem access [(#726)](getsentry/sentry-laravel#726)

  This behaviour can be changed in your config/sentry.php file.

  'breadcrumbs' => [
      // Capture storage access as breadcrumbs
      'storage' => true,
  ],
  `tracing` => [
      // Capture storage access as spans
      'storage' => true,
  ],
  

• GraphQL and HTTP client improvements [(#720)](getsentry/sentry-laravel#720)

  This adds an improved visual representation of the request body on the Sentry web interface, as well as response_body_size and request_body_size to HTTP client breadcrumbs.

• Less sensitive data send by default [(#732)](getsentry/sentry-laravel#732)

  The SDK will no longer send the value of the configured Laravel session cookie as well as the value of any cookies starting with remember_*. Additionally, SQL bindings are no longer set on breadcrumbs by default. This behaviour can be changed in your config/sentry.php file.

  'breadcrumbs' => [
      // Capture bindings on SQL queries logged in breadcrumbs
      'sql_bindings' => false,
  ],
  

• Make it configurable if performance traces continue after the response has been sent [(#727)](getsentry/sentry-laravel#727)

  This behaviour can be changed in your config/sentry.php file.

... (truncated)

Changelog

Sourced from sentry/sentry-laravel's changelog.

3.7.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.7.0.

Features

• Tracing without Performance [(#719)](getsentry/sentry-laravel#719)

  The SDK will now continue a trace from incoming HTTP requests, even if performance is not enabled. To continue a trace outward, you may attach the Sentry tracing headers to any HTTP client request. You can fetch the required header values by calling \Sentry\getBaggage() and \Sentry\getTraceparent().

• Add performance traces and breadcrumbs for filesystem access [(#726)](getsentry/sentry-laravel#726)

  This behaviour can be changed in your config/sentry.php file.

  'breadcrumbs' => [
      // Capture storage access as breadcrumbs
      'storage' => true,
  ],
  `tracing` => [
      // Capture storage access as spans
      'storage' => true,
  ],
  

• GraphQL and HTTP client improvements [(#720)](getsentry/sentry-laravel#720)

  This adds an improved visual representation of the request body on the Sentry web interface, as well as response_body_size and request_body_size to HTTP client breadcrumbs.

• Less sensitive data send by default [(#732)](getsentry/sentry-laravel#732)

  The SDK will no longer send the value of the configured Laravel session cookie as well as the value of any cookies starting with remember_*. Additionally, SQL bindings are no longer set on breadcrumbs by default. This behaviour can be changed in your config/sentry.php file.

  'breadcrumbs' => [
      // Capture bindings on SQL queries logged in breadcrumbs
      'sql_bindings' => false,
  ],
  

• Make it configurable if performance traces continue after the response has been sent [(#727)](getsentry/sentry-laravel#727)

  This behaviour can be changed in your config/sentry.php file.

... (truncated)

Commits

• f6f6431 release: 3.7.0
• 4a99a29 Prepare 3.7.0 (#744)
• 73de267 Handle exceptions raised while resolving the request (#743)
• fd60f0e Update default config file with env for everything and added docs (#735)
• 2d45a88 Add tracing for storage access (#726)
• 7760e70 Less sensitive data by default (#732)
• 9b26cad Make it configurable if the performance traces continues after the response h...
• e950109 GraphQL and HTTP client improvements (#720)
• a97d5eb Delete stale.yml (#730)
• cd3580f Create GH issue templates (#728)
• 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 #366.