Skip to content

Bump sentry-ruby from 6.3.1 to 6.5.0#134

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/bundler/sentry-ruby-6.5.0
Open

Bump sentry-ruby from 6.3.1 to 6.5.0#134
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/bundler/sentry-ruby-6.5.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 16, 2026

Bumps sentry-ruby from 6.3.1 to 6.5.0.

Changelog

Sourced from sentry-ruby's changelog.

6.5.0

New Features ✨

Bug Fixes 🐛

Internal Changes 🔧

6.4.1

Bug Fixes 🐛

6.4.0

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)

... (truncated)

Commits
  • a34b047 release: 6.5.0
  • d61d271 fix: Copy event processors on Scope#dup (#2893)
  • 8205acb fix(release-detector): Prefer HEROKU_BUILD_COMMIT over deprecated HEROKU_SLUG...
  • 2c1c8b7 feat(transport): Handle HTTP 413 response for oversized envelopes (#2885)
  • 5685885 fix: Don't transform attributes in place in metrics (#2883)
  • d8352b6 test: fix flaky request timing tests (#2882)
  • cfcab4b feat: Implement strict trace continuation (#2872)
  • a640799 release: 6.4.1
  • 66c2ad1 fix(rails): Track request queue time in Rails middleware (#2877)
  • 38b827d release: 6.4.0
  • Additional commits viewable in compare view

Dependabot compatibility score

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 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)

Bumps [sentry-ruby](https://github.com/getsentry/sentry-ruby) from 6.3.1 to 6.5.0.
- [Release notes](https://github.com/getsentry/sentry-ruby/releases)
- [Changelog](https://github.com/getsentry/sentry-ruby/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-ruby@6.3.1...6.5.0)

---
updated-dependencies:
- dependency-name: sentry-ruby
  dependency-version: 6.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file ruby Pull requests that update ruby code labels Mar 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file ruby Pull requests that update ruby code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants