chore(deps): bump sentry/sentry-laravel from 4.4.1 to 4.5.1

[dependabot[bot]]

Bumps sentry/sentry-laravel from 4.4.1 to 4.5.1.

Release notes

Sourced from sentry/sentry-laravel's releases.

4.5.1

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

Bug Fixes

• Fix discarded attribute violation reporter not accepting multiple property names [(#890)](getsentry/sentry-laravel#890)

4.5.0

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

Features

• Limit when SQL query origins are being captured [(#881)](getsentry/sentry-laravel#881)

  We now only capture the origin of a SQL query when the query is slower than 100ms, configurable by the SENTRY_TRACE_SQL_ORIGIN_THRESHOLD_MS environment variable.

• Add tracing and breadcrumbs for Notifications [(#852)](getsentry/sentry-laravel#852)

• Add reporter for Model::preventAccessingMissingAttributes() [(#824)](getsentry/sentry-laravel#824)

• Make it easier to enable the debug logger [(#880)](getsentry/sentry-laravel#880)

  You can now enable the debug logger by adding the following to your config/sentry.php file:

  'logger' => Sentry\Logger\DebugFileLogger::class, // This will log SDK logs to `storage_path('logs/sentry.log')`
  

  Only use this in development and testing environments, as it can generate a lot of logs.

Bug Fixes

• Fix Lighthouse operation not detected when query contained a fragment before the operation [(#883)](getsentry/sentry-laravel#883)

• Fix an exception being thrown when the username extracted from the authenticated user model is not a string [(#887)](getsentry/sentry-laravel#887)

Changelog

Sourced from sentry/sentry-laravel's changelog.

4.5.1

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

Bug Fixes

• Fix discarded attribute violation reporter not accepting multiple property names [(#890)](getsentry/sentry-laravel#890)

4.5.0

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

Features

• Limit when SQL query origins are being captured [(#881)](getsentry/sentry-laravel#881)

  We now only capture the origin of a SQL query when the query is slower than 100ms, configurable by the SENTRY_TRACE_SQL_ORIGIN_THRESHOLD_MS environment variable.

• Add tracing and breadcrumbs for Notifications [(#852)](getsentry/sentry-laravel#852)

• Add reporter for Model::preventAccessingMissingAttributes() [(#824)](getsentry/sentry-laravel#824)

• Make it easier to enable the debug logger [(#880)](getsentry/sentry-laravel#880)

  You can now enable the debug logger by adding the following to your config/sentry.php file:

  'logger' => Sentry\Logger\DebugFileLogger::class, // This will log SDK logs to `storage_path('logs/sentry.log')`
  

  Only use this in development and testing environments, as it can generate a lot of logs.

Bug Fixes

• Fix Lighthouse operation not detected when query contained a fragment before the operation [(#883)](getsentry/sentry-laravel#883)

• Fix an exception being thrown when the username extracted from the authenticated user model is not a string [(#887)](getsentry/sentry-laravel#887)

Commits

• a15b2f5 release: 4.5.1
• f84c9a4 Prepare 4.5.1 (#891)
• 0c2fc7b Fix discarded attribute violation reporter not accepting multiple property na...
• 44345a9 Merge branch 'release/4.5.0'
• cdcd362 release: 4.5.0
• 1cdaea4 Prepare 4.5.0 (#888)
• 0378a40 Fix username not being a string resulting in exception (#887)
• fefacb9 Refactor model violation reporters (#825)
• 300bb6f Limit cases where SQL origin is captured (#881)
• 3fd21f9 LighthouseIntegration: Fix finding the operation definition node on the query...
• 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)