Bump sentry-ruby from 4.2.1 to 5.7.0

[dependabot]

Bumps sentry-ruby from 4.2.1 to 5.7.0.

Changelog

Sourced from sentry-ruby's changelog.

5.7.0

Features

• Expose span_id in Span constructor #1945
• Expose end_timestamp in Span#finish and Transaction#finish #1946
• Add Transaction#set_context api #1947
• Add OpenTelemetry support with new sentry-opentelemetry gem

  • Add config.instrumenter to switch between :sentry and :otel instrumentation #1944

    The new sentry-opentelemetry gem adds support to automatically integrate OpenTelemetry performance tracing with Sentry. Give it a try and let us know if you have any feedback or problems with using it.

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. Also make sure to update your traces_sampler if you rely on the op for filtering some requests.

Refactoring

• Make transaction a required argument of Span #1921

... (truncated)

Commits

• cf39981 release: 5.7.0
• 5ba3268 Fix bad link in changelog (#1953)
• 1b39e7e Add new sentry-opentelemetry gem (#1948)
• 3567021 Pin jruby to 9.3 for sentry-raven (#1951)
• b3291a5 Add Transaction#set_context api (#1947)
• 3fad30c Expose optional end_timestamp argument in Span#finish and Transaction#finish ...
• fa98335 Expose span_id in Span constructor (#1945)
• a62fb2d Add config.instrumenter to switch between sentry and otel instrumentation (#1...
• f78a284 Adjust tests for jruby 9.4 (#1949)
• 5bfdf80 Clarify op change for traces_sampler usage (#1939)
• 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)