Bump sentry-rails from 5.23.0 to 5.25.0

[dependabot]

Bumps sentry-rails from 5.23.0 to 5.25.0.

Changelog

Sourced from sentry-rails's changelog.

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|
    # ... your setup ...
    config.enable_logs = true
  end

  Once you configured structured logging, you get access to a new Sentry.logger object that can be used as a regular logger with additional structured data support:

  Sentry.logger.info("User logged in", user_id: 123)
  Sentry.logger.error("Failed to process payment",
  transaction_id: "tx_123",
  error_code: "PAYMENT_FAILED"
  )

  You can also use message templates with positional or hash parameters:

... (truncated)

Commits

• 975c2b1 release: 5.25.0
• de9f210 Fix coverage by making sure isolated specs have SimpleCov.command_name (#2629)
• cad4b3f release: 5.24.0
• 63b5162 Replace logger with sdk_logger (#2621)
• 33d0b5d Introduce active_job_report_on_retry_error (#2617)
• 8c699de [active_job] report on each retry failure (#2598)
• 5e8db8d Fix jruby on CI (#2609)
• 9cd3b2e Only expose ActiveStorage keys on span data if send_default_pii is on (#2589)
• 7db2c29 [active_job] support exception reporting only after last retry failed (#2573)
• See full diff 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 #253.