Bump sentry-rails from 5.17.3 to 5.20.0

[dependabot[bot]]

Bumps sentry-rails from 5.17.3 to 5.20.0.

Changelog

Sourced from sentry-rails's changelog.

5.20.0

• Add support for $SENTRY_DEBUG and $SENTRY_SPOTLIGHT (#2374)
• Support human readable intervals in sidekiq-cron (#2387)
• Set default app dirs pattern (#2390)
• Add new strip_backtrace_load_path boolean config (default true) to enable disabling load path stripping (#2409)

Bug Fixes

• Fix error events missing a DSC when there's an active span (#2408)
• Verifies presence of client before adding a breadcrumb (#2394)
• Fix Net:HTTP integration for non-ASCII URI's (#2417)
• Prevent Hub from having nil scope and client (#2402)

5.19.0

Features

• Use Concurrent.available_processor_count instead of Concurrent.usable_processor_count (#2358)

• Support for tracing Faraday requests (#2345)

  • Closes #1795
  • Please note that the Faraday instrumentation has some limitations in case of async requests: lostisland/faraday#1381

  Usage:

  Sentry.init do |config|
    # ...
    config.enabled_patches << :faraday
  end
  

• Support for attachments (#2357)

  Usage:

  Sentry.add_attachment(path: '/foo/bar.txt')
  Sentry.add_attachment(filename: 'payload.json', bytes: '{"value": 42}'))
  

• Transaction data are now included in the context (#2365)

  • Closes #2363

• Inject Sentry meta tags in the Rails application layout automatically in the generator (#2369)

  To turn this behavior off, use

... (truncated)

Commits

• 34ba320 release: 5.20.0
• 6181b7b Support Rails 7.2 on CI (#2382)
• 5c26b9e Fix rubocop setup (for some envs) (#2377)
• 43c5cc2 release: 5.19.0
• a09da50 Include Sentry meta tag in the layout automatically (#2369)
• cdf8a4a release: 5.18.2
• 36866c5 Make links more specific in gemspecs (#2311)
• 90edcb8 Fix typos (#2332)
• 9a2b5ba release: 5.18.1
• 653b06f Drop Gem::Specification's usage so it doesn't break bundler standalone (#2335)
• 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 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[bot]]

Superseded by #1595.