chore(deps): bump sentry-ruby from 5.20.1 to 5.26.0

[dependabot]

Bumps sentry-ruby from 5.20.1 to 5.26.0.

Changelog

Sourced from sentry-ruby's changelog.

5.26.0

Feature

• Support for :logger patch which enables sending logs to Sentry when enabled_logs is set to true (#2657)

  Here's a sample config:

  Sentry.init do |config|
    # ... your setup ...
    config.enable_logs = true
    config.enabled_patches = [:logger]
  end

Bug Fixes

• Skip creating LogEventBuffer if logging is not enabled (#2652)

5.25.0

Features

• Support for before_send_log (#2634)
• Default user attributes are now automatically added to logs (#2647)

Bug Fixes

• Structured logging consumes way less memory now (#2643)

5.24.0

Features

• Add new sidekiq config report_only_dead_jobs (#2581)

• Add max_nesting of 10 to breadcrumbs data serialization (#2583)

• Add sidekiq config propagate_traces to control trace header injection (#2588)

  If you use schedulers you can get one large trace with all your jobs which is undesirable. We recommend using the following to propagate traces only from the Rails server and not elsewhere.

  config.sidekiq.propagate_traces = false unless Rails.const_defined?('Server')

• Only expose active_storage keys on span data if send_default_pii is on (#2589)

• Add new Sentry.logger for Structured Logging feature (#2620).

  To enable structured logging you need to turn on the enable_logs configuration option:

  Sentry.init do |config|

... (truncated)

Commits

• 218fda2 release: 5.26.0
• 1e377d6 Tests for Rails.logger when :logger patch is enabled (#2659)
• eeaeb2a Logger support (#2657)
• 32ca39e Skip creating LogEventBuffer if logging is not enabled (#2652)
• 975c2b1 release: 5.25.0
• 6b41b9c Add user attributes to logs (#2647)
• e126f72 Optimize LogEvent to reduce memory consumption (#2643)
• 35c5214 [devcontainer] switch to /workspace/sentry (#2645)
• 55ccf6b docs: add warning about unmaintained example and sample code (#2646)
• 213558f [sentry-ruby] fix and improve spec suite setup (#2640)
• 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)

[dependabot]

Superseded by #548.