Bump sentry/sentry-laravel from 3.0.0 to 3.3.2

[dependabot[bot]]

Bumps sentry/sentry-laravel from 3.0.0 to 3.3.2.

Release notes

Sourced from sentry/sentry-laravel's releases.

3.3.2

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

Bug Fixes

• Fix "Object of class Closure could not be converted to string" error when tracing redis_commands [(#668)](getsentry/sentry-laravel#668)

3.3.1

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

Bug Fixes

• Fix scheduled commands running in the background not reporting success/failure [(#664)](getsentry/sentry-laravel#664)

3.3.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.3.0. This release adds initial support for Cron Monitoring as well as new performance spans and breadcrumbs.

Warning Cron Monitoring is currently in beta. Beta features are still in-progress and may have bugs. We recognize the irony. If you have any questions or feedback, please email us at crons-feedback@sentry.io, reach out via Discord (#cronjobs), or open an issue.

Features

• Add inital support for Cron Monitoring [(#659)](getsentry/sentry-laravel#659)

  After creating your Cron Monitor on https://sentry.io, you can add the sentryMonitor() macro to your scheduled tasks defined in your app/Console/Kernel.php file. This will let Sentry know if your scheduled task started, whether the task was successful or failed, and its duration.

  protected function schedule(Schedule $schedule)
  {
      $schedule->command('emails:send')
          ->everyHour()
          ->sentryMonitor('<your-monitor-slug>'); // add this line
  }
  

• Add Livewire tracing integration [(#657)](getsentry/sentry-laravel#657)

  You can enable this feature by adding new config options to your config/sentry.php file.

  'breadcrumbs' => [
      // Capture Livewire components in breadcrumbs
      'livewire' => true,
  ],
  'tracing' => [
      // Capture Livewire components as spans
      'livewire' => true,
  

... (truncated)

Changelog

Sourced from sentry/sentry-laravel's changelog.

3.3.2

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

Bug Fixes

• Fix "Object of class Closure could not be converted to string" error when tracing redis_commands [(#668)](getsentry/sentry-laravel#668)

3.3.1

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

Bug Fixes

• Fix scheduled commands running in the background not reporting success/failure [(#664)](getsentry/sentry-laravel#664)

3.3.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Laravel SDK v3.3.0. This release adds initial support for Cron Monitoring as well as new performance spans and breadcrumbs.

Warning Cron Monitoring is currently in beta. Beta features are still in-progress and may have bugs. We recognize the irony. If you have any questions or feedback, please email us at crons-feedback@sentry.io, reach out via Discord (#cronjobs), or open an issue.

Features

• Add inital support for Cron Monitoring [(#659)](getsentry/sentry-laravel#659)

  After creating your Cron Monitor on https://sentry.io, you can add the sentryMonitor() macro to your scheduled tasks defined in your app/Console/Kernel.php file. This will let Sentry know if your scheduled task started, whether the task was successful or failed, and its duration.

  protected function schedule(Schedule $schedule)
  {
      $schedule->command('emails:send')
          ->everyHour()
          ->sentryMonitor('<your-monitor-slug>'); // add this line
  }
  

• Add Livewire tracing integration [(#657)](getsentry/sentry-laravel#657)

  You can enable this feature by adding new config options to your config/sentry.php file.

  'breadcrumbs' => [
      // Capture Livewire components in breadcrumbs
      'livewire' => true,
  ],
  

... (truncated)

Commits

• c502e8b release: 3.3.2
• 4223925 Prepare 3.3.2 (#669)
• eb0998f Validate first cache command argument type before using as string (#668)
• 138990b Merge branch 'release/3.3.1'
• a530699 release: 3.3.1
• b21eeda Update CHANGELOG.md (#667)
• 9eef821 Update README.md (#666)
• 7f91847 Prepare 3.3.1 (#665)
• b8d01bd Fix scheduled commands running in background not reporting success/failure (#...
• 263f41a Merge branch 'release/3.3.0'
• 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)

[stayallive]

@dependabot rebase

[dependabot[bot]]

Looks like sentry/sentry-laravel is up-to-date now, so this is no longer needed.