Bump sentry-rails from 4.9.2 to 5.0.1

[dependabot[bot]]

Bumps sentry-rails from 4.9.2 to 5.0.1.

Changelog

Sourced from sentry-rails's changelog.

5.0.1

• Don't reuse Net::HTTP objects in HTTPTransport #1696

5.0.0

Breaking Change - Goodbye faraday 👋

TL;DR: If you are already on version 4.9 and do not use config.transport.http_adapter and config.transport.faraday_builder, you don't need to change anything.

This version removes the dependency of faraday and replaces related implementation with the Net::HTTP standard library.

Why?

Since the old sentry-raven SDK, we've been using faraday as the HTTP client for years (see HTTPTransport). It's an amazing tool that saved us many work and allowed us to focus on SDK features.

But because many users also use faraday themselves and have their own version requirements, managing this dependency has become harder over the past few years. Just to list a few related issues:

• #944
• #1424
• #1524

And with the release of faraday 2.0, we could only imagine it getting even more difficult (which it kind of did, see #1663).

So we think it's time to say goodbye to it with this release.

What's changed?

By default, the SDK used faraday's net_http adapter, which is also built on top of Net::HTTP. So this change shouldn't impact most of the users.

The only noticeable changes are the removal of 2 faraday-specific transport configurations:

• config.transport.http_adapter
• config.transport.faraday_builder

If you are already on version 4.9 and do not use those configuration options, it'll be as simple as bundle update.

What if I still want to use faraday to send my events?

sentry-ruby already allows users to set a custom transport class with:

Sentry.init do |config|
  config.transport.transport_class = MyTransportClass
end

... (truncated)

Commits

• 3624312 release: 5.0.1
• c2f9e06 Don't reuse Net::HTTP objects in HTTPTransport (#1696)
• ee1cf06 Rails 7 example (#1694)
• 9380fbc Bump postcss from 7.0.32 to 7.0.39 in /sentry-rails/examples/rails-6.0 (#1670)
• 458d31c Bump lodash from 4.17.19 to 4.17.21 in /sentry-rails/examples/rails-6.0 (#1671)
• 665e10e Bump follow-redirects in /sentry-rails/examples/rails-6.0 (#1689)
• ae4113f Bump follow-redirects in /sentry-raven/examples/rails-6.0 (#1690)
• 308658b Merge branch 'release/5.0.0'
• 2aa80a8 release: 5.0.0
• fa56bc9 Update changelog
• 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)