Bump sentry-ruby from 5.15.2 to 5.16.0

[dependabot]

Bumps sentry-ruby from 5.15.2 to 5.16.0.

Changelog

Sourced from sentry-ruby's changelog.

5.16.0

Features

• Add backpressure handling for transactions #2185

  The SDK can now dynamically downsample transactions to reduce backpressure in high throughput systems. It starts a new BackpressureMonitor thread to perform some health checks which decide to downsample (halved each time) in 10 second intervals till the system is healthy again.

  To enable this behavior, use:

  Sentry.init do |config|
    # ...
    config.traces_sample_rate = 1.0
    config.enable_backpressure_handling = true
  end

  If your system serves heavy load, please let us know how this feature works for you!

• Implement proper flushing logic on close for Client Reports and Sessions #2206

• Support cron with timezone for sidekiq-scheduler patch #2209

  • Fixes #2187

• Add Cron::Configuration object that holds defaults for all MonitorConfig objects #2211

  Sentry.init do |config|
    # ...
    config.cron.default_checkin_margin = 1
    config.cron.default_max_runtime = 30
    config.cron.default_timezone = 'America/New_York'
  end

• Clean up logging #2216

• Pick up config.cron.default_timezone from Rails config #2213

• Don't add most scope data (tags/extra/breadcrumbs) to CheckInEvent #2217

Commits

• 21f94f8 release: 5.16.0
• 96f421e Changelog for 5.16.0 (#2219)
• e02c5fd Don't add most scope data to CheckInEvent (#2217)
• 918b83d Clean up logging (#2216)
• 49a628e Add comment for fugit (#2215)
• 3ea9e79 Pick up config.cron.default_timezone from Rails config (#2213)
• c9a79bf Improvements around the cron monitoring feature (#2212)
• 1fe52d1 Remove unnecessary Rake patch (#2214)
• babdd55 Add Ruby 3.3 to CI matrix (#2208)
• b420bf8 Allow setting defaults for MonitorConfig objects with new Cron::Confi… (#2211)
• 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)

[github-actions]

⚠️ This repo is Continuously Deployed: make sure you follow the guidance ⚠️

[floehopper]

@dependabot recreate

[floehopper]

It seems slightly odd that upgrading sentry-ruby from v5.15.2 -> v5.16.0 means that sentry-rails is downgraded from v5.15.2 to v5.3.1. However, I tried upgrading sentry-rails locally on this branch and bundler didn't want to do it. So I think this is probably fine!

[floehopper]

It seems slightly odd that upgrading sentry-ruby from v5.15.2 -> v5.16.0 means that sentry-rails is downgraded from v5.15.2 to v5.3.1. However, I tried upgrading sentry-rails locally on this branch and bundler didn't want to do it. So I think this is probably fine!

@jkempster34 spotted this issue which probably explains the above ☝️