Bump sentry/sentry-laravel from 1.1.0 to 2.6.0

[dependabot-preview]

Bumps sentry/sentry-laravel from 1.1.0 to 2.6.0.

Release notes

Sourced from sentry/sentry-laravel's releases.

2.6.0

• Add all log context as log_context to events when using the log channel (#489)
• Add integration to improve performance tracing for Laravel Lighthouse (#490)

2.5.3

• Correctly call flush on the PHP SDK client (#484)
• Fix errors on Laravel 5.x caused by Laravel not using nyholm/psr7 to generate PSR-7 request but older zendframework/zend-diactoros package which might not be available

2.5.2

• Fix problem with parsing uploaded files from request after they have been moved (#487)

2.5.1

• Fix problem with queue tracing when triggered from unit tests or when missing a queue name in the event

2.5.0

• Add sql.origin to SQL query spans with the file and line where the SQL query originated from (#398)
• Remove wrapper around the context of log entry breadcrumbs (#405)
• Ensure user integrations are always executed after SDK integrations (#474)
• Fix repeated booted callback registration from performance tracing middleware (#475)
• Add tracing support for queue jobs, enable with SENTRY_TRACE_QUEUE_ENABLED=true (#478)
• Add options to disable parts of performance tracing (#478)
• Remove string representation of exception from exceptions logged through log channels (#482)
• Use message from Monolog record to prevent bloating the log message being recorded with timestamps and log log level (#482)
• Add report_exceptions option to the Sentry log channel that can be set to false to not report exceptions (#482)

2.4.2

• Avoid collision if another package has bound sentry in the Laravel container (#467)

2.4.1

• Fix type hints incompatible with Laravel Lumen (#462)

2.4.0

• Read the request IP from the Laravel request to make it more accurate when behind a reverse proxy (requires trusted proxies to be setup correctly) (#419)
• Get request information (like the URL) from the Laravel request instead of constructing it from the global state (#419)
• Fix generated route name not correctly ignored when using prefix (#441)
• Fix overwriting the transaction name if it's set by the user (#442)
• Add result from optional context(): array method on captured exception to the event sent to Sentry (#457)
• Fix not overwriting the event transaction name if it was an empty string (#460)
• Bump Sentry SDK to 3.2.*

2.3.1

• Fix problems when enabling tracing on Laravel Lumen (#416)
• PHP 8 Support (#431)

2.3.0

• Bump Sentry SDK to 3.1.* (#420)

2.2.0

• Fix incorrectly stripped base controller action from transaction name (#406)
• Move tracing request/response data hydration to the tracing middleware (#408)

... (truncated)

Changelog

Sourced from sentry/sentry-laravel's changelog.

2.6.0

• Add all log context as log_context to events when using the log channel (#489)
• Add integration to improve performance tracing for Laravel Lighthouse (#490)

2.5.3

• Correctly call flush on the PHP SDK client (#484)
• Fix errors on Laravel 5.x caused by Laravel not using nyholm/psr7 to generate PSR-7 request but older zendframework/zend-diactoros package which might not be available

2.5.2

• Fix problem with parsing uploaded files from request after they have been moved (#487)

2.5.1

• Fix problem with queue tracing when triggered from unit tests or when missing a queue name in the event

2.5.0

• Add sql.origin to SQL query spans with the file and line where the SQL query originated from (#398)
• Remove wrapper around the context of log entry breadcrumbs (#405)
• Ensure user integrations are always executed after SDK integrations (#474)
• Fix repeated booted callback registration from performance tracing middleware (#475)
• Add tracing support for queue jobs, enable with SENTRY_TRACE_QUEUE_ENABLED=true (#478)
• Add options to disable parts of performance tracing (#478)
• Remove string representation of exception from exceptions logged through log channels (#482)
• Use message from Monolog record to prevent bloating the log message being recorded with timestamps and log log level (#482)
• Add report_exceptions option to the Sentry log channel that can be set to false to not report exceptions (#482)

2.4.2

• Avoid collision if another package has bound sentry in the Laravel container (#467)

2.4.1

• Fix type hints incompatible with Laravel Lumen (#462)

2.4.0

• Read the request IP from the Laravel request to make it more accurate when behind a reverse proxy (requires trusted proxies to be setup correctly) (#419)
• Get request information (like the URL) from the Laravel request instead of constructing it from the global state (#419)
• Fix generated route name not correctly ignored when using prefix (#441)
• Fix overwriting the transaction name if it's set by the user (#442)
• Add result from optional context(): array method on captured exception to the event sent to Sentry (#457)
• Fix not overwriting the event transaction name if it was an empty string (#460)
• Bump Sentry SDK to 3.2.*

2.3.1

... (truncated)

Commits

• 1a4db2b release: 2.6.0
• 2954ca1 Prepare 2.6.0
• 6a64f65 Laravel Lighthouse tracing integration (#490)
• 960046d Add missing changelog entry
• 89a418d Add logger context as extra context (#489)
• c982cbd Merge release/2.5.3 into master
• 23ea0d8 release: 2.5.3
• 3c85e34 Prepare 2.5.3
• c34ca91 Update zendframework/zend-diactoros suggest
• 96b3cf2 Add suggest for zendframework/zend-diactoros
• 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #268.