Update dependency sentry-ruby to v6.5.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
sentry-ruby (source, changelog)	6.2.0 → 6.5.0

---

Release Notes

getsentry/sentry-ruby (sentry-ruby)

v6.5.0

Compare Source

New Features ✨

• (otlp) Add collector_url option to OTLP integration by @​sl0thentr0py in #​2887
• (release-detector) Prefer HEROKU_BUILD_COMMIT over deprecated HEROKU_SLUG_COMMIT by @​ericapisani in #​2886
• Implement strict trace continuation by @​giortzisg in #​2872

Bug Fixes 🐛

• (rails) Set mechanism.handled based on error handling status by @​solnic in #​2892
• Copy event processors on Scope#dup by @​sl0thentr0py in #​2893
• Map trilogy database adapter to mysql for Query Insights compatibility by @​krismichalski in #​2656
• Don't transform attributes in place in metrics by @​sl0thentr0py in #​2883

Internal Changes 🔧

• (transport) Handle HTTP 413 response for oversized envelopes by @​sl0thentr0py in #​2885

v6.4.1

Compare Source

Bug Fixes 🐛

• (rails) Track request queue time in Rails middleware by @​dingsdax in #​2877

v6.4.0

Compare Source

Features

• Add support for OTLP ingestion in sentry-opentelemetry (#​2853)

  Sentry now has first class OTLP ingestion capabilities.

  Sentry.init do |config|
    ## ...
    config.otlp.enabled = true
  end

  Under the hood, this will setup:

  • An OpenTelemetry::Exporter that will automatically set up the OTLP ingestion endpoint from your DSN
    • You can turn this off with config.otlp.setup_otlp_traces_exporter = false to setup your own exporter
  • An OTLPPropagator that ensures Distributed Tracing works
    • You can turn this off with config.otlp.setup_propagator = false
  • Trace/Span linking for all other Sentry events such as Errors, Logs, Crons and Metrics

  If you were using the SpanProcessor before, we recommend migrating over to config.otlp since it's a much simpler setup.

• Treat Sidekiq nil retry as true (#​2864)

• Queue time capture for Rack (#​2838)

Bug Fixes

• Fix MetricEvent timestamp serialization to float (#​2862)
• Fix CGI imports for ruby 4.x (#​2863)
• Always include scope user data in telemetry (#​2866)

v6.3.1

Compare Source

Bug Fixes

• Use ActionDispatch::ExceptionWrapper for correct HTTP status code (#​2850)
• Add explicit dependency on logger gem to fix Ruby 4.0 warning (#​2837)

Internal

• Add external_propagation_context support (#​2841)

v6.3.0

Compare Source

Features

• Implement new Sentry.metrics functionality (#​2818)

  The SDK now supports Sentry's new Trace Connected Metrics product.

   Sentry.metrics.count("button.click", 1, attributes: { button_id: "submit" })
   Sentry.metrics.distribution("response.time", 120.5, unit: "millisecond")
   Sentry.metrics.gauge("cpu.usage", 75.2, unit: "percent")

  Metrics is enabled by default and only activates once you use the above APIs. To disable completely:

  Sentry.init do |config|
    # ...
    config.enable_metrics = false
  end

• Support for tracing Sequel queries (#​2814)

  require "sentry"
  require "sentry/sequel"
  
  Sentry.init do |config|
    config.enabled_patches << :sequel
  end
  
  DB = Sequel.sqlite
  DB.extension(:sentry)

• Add support for OpenTelemetry messaging/queue system spans (#​2685)

• Add support for config.std_lib_logger_filter proc (#​2829)

  Sentry.init do |config|
    config.std_lib_logger_filter = proc do |logger, message, severity|
      # Only send ERROR and above messages
      severity == :error || severity == :fatal
    end
  
    config.enabled_patches = [:std_lib_logger]
  end

Bug Fixes

• Handle empty frames case gracefully with local vars (#​2807)
• Handle more extra attribute types when using extra attributes for structured logging (#​2815)

  # This now works too and the nested hash is dumped to JSON string
  Sentry.logger.info("Hello World", extra: { today: Date.today, user_id: user.id })

• Prevent SDK crash when SDK logging fails (#​2817)

Internal

• Unify Logs and Metrics implementations (#​2826)
• Unify LogEventBuffer and MetricEventBuffer logic (#​2830)
• Add maximum limits on LogEventBuffer (1k) and MetricEventBuffer (10k) for protection from memory blowup (#​2831)
• Lazily start LogEventBuffer and MetricEventBuffer threads (#​2832)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 66.90%. Comparing base (ccc7493) to head (b817c0d).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #798   +/-   ##
=======================================
  Coverage   66.90%   66.90%           
=======================================
  Files          46       46           
  Lines        1281     1281           
=======================================
  Hits          857      857           
  Misses        424      424           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[yegor256]

@rultor please, try to merge, since 13 checks have passed

[rultor]

@rultor please, try to merge, since 13 checks have passed

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here.

[rultor]

@rultor please, try to merge, since 13 checks have passed

@renovate[bot] @yegor256 Oops, I failed. You can see the full log here (spent 1min).

'pid' file is absent on the server after the end of operation; it seems that we didn't manage to start Docker container correctly