Bump sentry-rails from 5.5.0 to 5.6.0

[dependabot[bot]]

Bumps sentry-rails from 5.5.0 to 5.6.0.

Changelog

Sourced from sentry-rails's changelog.

5.6.0

Features

• Allow users to configure their asset-skipping pattern #1915

  Users can now configure their own pattern to skip asset requests' transactions

  Sentry.init do |config|
    config.rails.assets_regexp = /my_regexp/
  end
  

• Use Sentry.with_child_span in redis and net/http instead of span.start_child #1920

  • This might change the nesting of some spans and make it more accurate
  • Followup fix to set the sentry-trace header in the correct place #1922

• Use Exception#detailed_message when generating exception message if applicable #1924

• Make sentry-sidekiq compatible with Sidekiq 7 #1930

Bug Fixes

• Sentry::BackgroundWorker will release ActiveRecord connection pool only when the ActiveRecord connection is established

• Remove bad encoding arguments in redis span descriptions #1914

  • Fixes #1911

• Add missing initialized? checks to sentry-rails #1919

  • Fixes #1885

• Update Tracing Span's op names #1923

  Currently, Ruby integrations' Span op names aren't aligned with the core specification's convention, so we decided to update them altogether in this PR. If you rely on Span op names for fine-grained event filtering, this may affect the data your app sends to Sentry.

Refactoring

• Make transaction a required argument of Span #1921

Commits

• 4e3f237 release: 5.6.0
• 0881f54 Update changelog entry (#1933)
• 6b35110 Make sentry-sidekiq compatible with Sidekiq 7 (#1930)
• ca597ad Lock sentry-raven's sidekiq to < 7.0 (#1929)
• 69073ab Update Tracing Span's op names (#1923)
• 279df83 Fix setting the sentry-trace header in net/http (#1922)
• 29c444b Make transaction a required argument of Span (#1921)
• 7d97914 Use Exception#detailed_message when generating exception message if applica...
• a1fda66 Fix return in do..end block (#1926)
• 4865399 chore(ci): add dangerJS to police CHANGELOG.md (#1925)
• 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 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)