chore: Bump sentry from 8.1.0 to 11.0.4

[dependabot]

Bumps sentry from 8.1.0 to 11.0.4.

Release notes

Sourced from sentry's releases.

11.0.4

• Fix safe JSON encoding of improper lists (#938)

11.0.3

Various improvements

• Allow any version of opentelemetry deps and verify minimum versions internally - this makes it possible to use sentry with tracing disabled along with older versions of opentelemetry deps (#931)

11.0.2

Bug fixes

• Deeply nested spans are handled now when building up traces in SpanProcessor (#924)

Various improvements

• Span's attributes no longer include db.url: "ecto:" entries as they are now filtered out (#925)

11.0.1

Various improvements

• Sentry.OpenTelemetry.Sampler now works with an empty config (#915)

11.0.0

This release comes with a beta support for Traces using OpenTelemetry - please test it out and report any issues you find.

New features

• Beta support for Traces using OpenTelemetry (#902)

  To enable Tracing in your Phoenix application, you need to add the following to your mix.exs:

  def deps do
    [
      # ...
      {:sentry, "~> 11.0.0"},
      {:opentelemetry, "~> 1.5"},
      {:opentelemetry_api, "~> 1.4"},
      {:opentelemetry_exporter, "~> 1.0"},
      {:opentelemetry_semantic_conventions, "~> 1.27"},
      {:opentelemetry_phoenix, "~> 2.0"},
      {:opentelemetry_ecto, "~> 1.2"},
      # ...
    ]
  

  And then configure Tracing in Sentry and OpenTelemetry in your config.exs:

  config :sentry,

... (truncated)

Changelog

Sourced from sentry's changelog.

11.0.4

• Fix safe JSON encoding of improper lists (#938)

11.0.3

Various improvements

• Allow any version of opentelemetry deps and verify minimum versions internally - this makes it possible to use sentry with tracing disabled along with older versions of opentelemetry deps (#931)

11.0.2

Bug fixes

• Deeply nested spans are handled now when building up traces in SpanProcessor (#924)

Various improvements

• Span's attributes no longer include db.url: "ecto:" entries as they are now filtered out (#925)

11.0.1

Various improvements

• Sentry.OpenTelemetry.Sampler now works with an empty config (#915)

11.0.0

This release comes with a beta support for Traces using OpenTelemetry - please test it out and report any issues you find.

New features

• Beta support for Traces using OpenTelemetry (#902)

  To enable Tracing in your Phoenix application, you need to add the following to your mix.exs:

  def deps do
    [
      # ...
      {:sentry, "~> 11.0.0"},
      {:opentelemetry, "~> 1.5"},
      {:opentelemetry_api, "~> 1.4"},
      {:opentelemetry_exporter, "~> 1.0"},
      {:opentelemetry_semantic_conventions, "~> 1.27"},
      {:opentelemetry_phoenix, "~> 2.0"},
      {:opentelemetry_ecto, "~> 1.2"},
      # ...
    ]
  

... (truncated)

Commits

• 5f5dc03 release: 11.0.4
• 78bf227 Fix safe JSON encoding of improper lists (#938)
• 5bf38d6 Update pull_request_template.md (#941)
• 0de7beb meta: add pull request template (#940)
• be47217 Update SDK version in the README.md (#930)
• 78b7f5a Merge branch 'release/11.0.3'
• 14b95fd release: 11.0.3
• 0f1c3dd Update CHANGELOG.md for 11.0.3 (#935)
• 913ecff Relax version reqs on opentelemetry deps (#931)
• f83b508 Merge branch 'release/11.0.2'
• 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]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

[jzimbel-mbta]

Upgrade guides to check through:

• 8 -> 9
• 9 -> 10
• 10 -> 11 (Seems like there are no breaking changes in 11.x, just new features)

[jzimbel-mbta]

I wanted to add some regression tests to the event filtering module for more confidence that the new code matches the behavior of the old, but Sentry.Test module does not exist until v10.2.0.

So the new code is tested, but not the old. I'll try to do some manual testing in dev-green to make up for it.

[jzimbel-mbta]

I temporarily added an endpoint to raise an exception that shouldn't be filtered out, and it made it to Sentry as expected, including the code stacktrace. https://mbtace.sentry.io/issues/6963904771/events/eabf61c8c04c495188fd3d3bd25f2da6/

Looking good, so I'm going to address the lockfile conflict and then assign someone to review my changes.