⬆️ Bump sentry-ruby from 5.12.0 to 5.19.0 in /dhcp-service/metrics

[dependabot]

Bumps sentry-ruby from 5.12.0 to 5.19.0.

Changelog

Sourced from sentry-ruby's changelog.

5.19.0

Features

• Use Concurrent.available_processor_count instead of Concurrent.usable_processor_count (#2358)

• Support for tracing Faraday requests (#2345)

  • Closes #1795
  • Please note that the Faraday instrumentation has some limitations in case of async requests: lostisland/faraday#1381

• Support for attachments (#2357)

  Usage:

  Sentry.add_attachment(path: '/foo/bar.txt')
  Sentry.add_attachment(filename: 'payload.json', bytes: '{"value": 42}'))

• Transaction data are now included in the context (#2365)

  • Closes #2364

• Inject Sentry meta tags in the Rails application layout automatically in the generator (#2369)

  To turn this behavior off, use

  bin/rails generate sentry --inject-meta false

Bug Fixes

• Fix skipping connect spans in open-telemetry #2364

5.18.2

Bug Fixes

• Don't overwrite ip_address if already set on user #2350
  • Fixes #2347
• teardown_sentry_test helper should clear global even processors too (#2342)
• Suppress the unnecessary “unsupported options notice” (#2349)

Internal

• Use Concurrent.usable_processor_count when it is available (#2339)
• Report dropped spans in Client Reports (#2346)

5.18.1

Bug Fixes

• Drop Gem::Specification's usage so it doesn't break bundler standalone (#2335)

... (truncated)

Commits

• 43c5cc2 release: 5.19.0
• 8c1c259 Use Concurrent.available_processor_count instead of `Concurrent.usable_proc...
• 837577a File/attachment uploads (#2357)
• 47c4458 Include transaction data in the trace context (#2365)
• e4571d9 Remove upper limit on graphql gem version (#2362)
• ef1eeb3 Unify Net::HTTP and Faraday implementations (#2360)
• 09f348e Support for tracing Faraday requests (#2345)
• cdf8a4a release: 5.18.2
• c785d04 Add client reports for span drop counts (#2346)
• c16a0f2 Don't overwrite ip_address if already set on user (#2350)
• 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 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.