Update sentry-rails 5.21.0 → 5.22.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ sentry-rails (5.21.0 → 5.22.0) · Repo · Changelog

Release Notes

5.22.0

Features

• Add include_sentry_event matcher for RSpec #2424

• Add support for Sentry Cache instrumentation, when using Rails.cache #2380

• Add support for Queue Instrumentation for Sidekiq. #2403

• Add support for string errors in error reporter (#2464)

• Reset trace_id and add root transaction for sidekiq-cron #2446

• Add support for Excon HTTP client instrumentation (#2383)

  Note: MemoryStore and FileStore require Rails 8.0+

Bug Fixes

• Fix Vernier profiler not stopping when already stopped #2429
• Fix send_default_pii handling in rails controller spans #2443
  • Fixes #2438
• Fix RescuedExceptionInterceptor to handle an empty configuration #2428
• Add mutex sync to SessionFlusher aggregates #2469
  • Fixes #2468
• Fix sentry-rails' backtrace cleaner issues (#2475)
  • Fixes #2472

Does any of this look wrong? Please let us know.

✳️ sentry-ruby (5.21.0 → 5.22.0) · Repo · Changelog

Release Notes

5.22.0

Features

• Add include_sentry_event matcher for RSpec #2424

• Add support for Sentry Cache instrumentation, when using Rails.cache #2380

• Add support for Queue Instrumentation for Sidekiq. #2403

• Add support for string errors in error reporter (#2464)

• Reset trace_id and add root transaction for sidekiq-cron #2446

• Add support for Excon HTTP client instrumentation (#2383)

  Note: MemoryStore and FileStore require Rails 8.0+

Bug Fixes

• Fix Vernier profiler not stopping when already stopped #2429
• Fix send_default_pii handling in rails controller spans #2443
  • Fixes #2438
• Fix RescuedExceptionInterceptor to handle an empty configuration #2428
• Add mutex sync to SessionFlusher aggregates #2469
  • Fixes #2468
• Fix sentry-rails' backtrace cleaner issues (#2475)
  • Fixes #2472

Does any of this look wrong? Please let us know.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)