Skip to content

chore(deps): update dependency sentry to v11 #299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update dependency sentry to v11 #299

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 17, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
sentry (source) prod major ~> 8.0 -> ~> 11.0

Release Notes

getsentry/sentry-elixir (sentry)

v11.0.3

Compare Source

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)

v11.0.2

Compare Source

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)

v11.0.1

Compare Source

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

v11.0.0

Compare Source

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`:

```elixir
config :sentry,

### ...
  traces_sample_rate: 1.0 # any value between 0 and 1.0 enables tracing

config :opentelemetry, span_processor: {Sentry.OpenTelemetry.SpanProcessor, []}
config :opentelemetry, sampler: {Sentry.OpenTelemetry.Sampler, []}
  • Add installer (based on Igniter) (#​876)
Various improvements
  • Tweak credit card regex handling for OTP-28 (#​898)

v10.10.0

Compare Source

This release adds Telemetry crash reporting, fixes compatibility with Erlang/OTP 28, and includes several bug fixes.

New features
  • Add Telemetry integration for capturing Telemetry crash events in Sentry (#​887 by @​whatyouhide)
  • Add :owner option for check-ins, providing more control over cron monitoring (#​879 by @​Miradorn)
Bug fixes
Various improvements

v10.9.0

Compare Source

This release adds a bunch of new features and fixes a few papercut bugs.

New features
  • Add :tags_from_metadata option to Sentry.LoggerHandler. Use this to better structure reports that come from logs (#​840 by @​icehaunter).
  • Add :discard_threshold option to Sentry.LoggerHandler to implement load shedding when the logger gets overloaded.
  • If you want to use Elixir 1.18's new JSON module, now you can (#​845).
  • Add :in_app_otp_apps configuration option. This should replace :in_app_module_allow_list for most use cases, making configuration simpler (#​854 by @​solnic).
  • Add support for per-module custom options for check ins. This means you can now configure single Oban (or Quantum) jobs with per-worker options such as timezones and more (#​833 by @​savhappy).
  • Add a global :extra config that can be set at the :sentry application level (akin to :tags today).
  • Improve Oban error reporting.
Bug fixes
  • We now deduplicate identical events significantly less, reducing the risk of not reporting events that are not duplicates.
  • When dropping breadcrumbs (because of the limit being reached), we now retain newest breadcrumbs instead of older ones (#​858 by @​dajinchu).
  • Ensure log messages are not captured with :capture_log_messages is false (#​865 by @​joladev).
  • Normalize Oban exception reasons for better reports.

v10.8.1

Compare Source

Various fixes & improvements

v10.8.0

Compare Source

This release bumps the minimum Elixir requirement to 1.13, fixes a few bugs, and introduces client reports. Client reports will be sent to Sentry by default, but you can disable them with:

config :sentry,

v10.7.1

Compare Source

Various fixes & improvements

v10.7.0

Compare Source

Various fixes & improvements

New features:

  • Add Sentry.ClientError for more structured client errors. You can use this to programmatically deal with errors when reporting events, if you need to. — @​savhappy
  • Add :integration_meta key to Sentry.Event. — (#​771) by @​savhappy
  • Validate Sentry options even if DSN is not set. — (#​772) by @​savhappy

Bug fixes:

  • Fix Sentry check-ins by internally mapping check-in IDs for "start" and "stop" events. — @​savhappy
  • Fix mix sentry.package_source_code edge cases by compiling code before running the task. — @​whatyouhide
  • Support structured logs in Sentry.LoggerHandler. — (#​765) by @​martosaur
  • Handle nil environment correctly in Sentry config — (#​753) by @​fahchen
  • Fix exceptions with an empty stacktrace. — (#​755) by @​savhappy

v10.6.2

Compare Source

Various fixes & improvements

v10.6.1

Compare Source

Various fixes & improvements

v10.6.0

Compare Source

Various fixes & improvements
  • Add overload protection to :logger handler (#​727).
  • Expose DSN via new Sentry.get_dsn/0 (#​731).
  • Fix a bug with nameless Quantum cron jobs support in the Quantum integration.

v10.5.0

Compare Source

Various fixes & improvements

v10.4.0

Compare Source

Various fixes & improvements
  • Add rate-limiting to Sentry.LoggerHandler.
  • Improve reporting of process crashes in Sentry.LoggerHandler.
  • Fix loading configuration in mix sentry.send_test_event.
  • Fix JSON libraries that raise errors when encoding.
  • Allow Sentry.LoggerBackend and Sentry.LoggerHandler to use Sentry metadata.
  • Validate configuration passed to Sentry.LoggerHandler.

v10.3.0

Compare Source

Various fixes & improvements

v10.2.1

Compare Source

Various fixes & improvements

v10.2.0

Compare Source

New features
  • Add support for Sentry Cron monitoring, with built-in support for Oban and Quantum.
  • Add Sentry.capture_check_in/1, which can be used to manually check-in crons.
  • Add --output flag for the mix sentry.package_source_code task. This can be useful for read-only build environments.
  • Introduce testing helpers in Sentry.Test.
  • Add the :url_scrubber option to Sentry.PlugContext.
Various fixes & improvements
  • Improve error message on unavailable config.

v10.1.0

Compare Source

Various fixes & improvements
  • Add Sentry.Interfaces.Thread to fix stacktraces in messages.
  • Add the --type and --no-stacktrace flags to mix sentry.send_test_message.
  • Add support for interpolating messages (with %s) placeholders. See Sentry.capture_message/2.
  • Add support for attachments; see Sentry.Attachment and Sentry.Context.add_attachment/1.

v10.0.3

Compare Source

Various fixes & improvements

v10.0.2

Compare Source

Various fixes & improvements

v10.0.1

Compare Source

Various fixes & improvements
  • Fix reading of config in "mix sentry.package_source_code" (#​653)
  • Don't ship Dialyzer PLTs with releases (#​654)

v10.0.0

Compare Source

9.x -> 10.0 Upgrade Guide

  • :report_deps now reports all loaded applications at the time the :sentry application starts. This is not a compile-time configuration option anymore.
  • Add the mix sentry.package_source_code Mix task. See the upgrade guide for more information.
  • Add ~r"/test/" to the default source code exclude patterns (see the :source_code_exclude_patterns option).
  • :environment_name now defaults to production (if it wasn't configured explicitly and if the SENTRY_ENVIRONMENT environment variable is not set).
  • Hard-deprecate :included_environments. To control whether to send events to Sentry, use the :dsn configuration option instead. :included_environments now emits a warning if used, but will still work until v11.0.0 of this library.
  • Hard-deprecate :before_send_event in favor of the new :before_send. This brings this SDK in line with all other Sentry SDKs.

v9.1.0

Compare Source

Various fixes & improvements

v9.0.0

Compare Source

8.x -> 9.0 Upgrade Guide

Breaking changes
  • Removed Sentry.Sources
  • Removed Sentry.Client, as it's an internal module
  • Removed the Sentry.Event.sentry_exception/0 type
  • Removed Sentry.Event.add_metadata/1
  • Removed Sentry.Event.culprit_from_stacktrace/1
  • Removed Sentry.Event.do_put_source_context/3
  • Removed the :async value for the :result option in Sentry.send_event/2 (and friends)
  • Removed Sentry.CrashError — now, crash reports (detected through Sentry.LoggerBackend) that do not contain exceptions are reported as messages in Sentry
  • Changed the shape of the Sentry.Event struct - check out the new fields (and typespec for Sentry.Event.t/0)
Various fixes & improvements
  • Add Sentry.LoggerHandler, which is a :logger handler rather than a Logger backend
  • Make the Sentry.HTTPClient.child_spec/0 callback optional
  • Add :all as a possible value of the :metadata configuration option for Sentry.LoggerBackend
  • Add :all as a possible value for the :included_environment configuration option
  • Add Sentry.Interfaces with all the child modules, which are useful if you're working directly with the Sentry API
  • Fix an issue with JSON-encoding non-encodable terms (such as PIDs, which are pretty common)
Deprecations
  • Soft-deprecate Sentry.EventFilter in favour of :before_send_event callbacks.
Various fixes & improvements

v8.1.0

Compare Source

Various fixes & improvements

Plus 14 more

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.

@renovate Renovate
Copy link
Author

renovate bot commented Jun 17, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: mix.lock
Command failed: mix deps.update sentry
** (Mix) Hex dependency resolution failed

@renovate renovate bot changed the title chore(deps): update dependency sentry to v11 chore(deps): update dependency sentry to v11 - autoclosed Jul 31, 2025
@renovate renovate bot closed this Jul 31, 2025
@renovate renovate bot deleted the renovate/sentry-11.x branch July 31, 2025 06:30
@renovate renovate bot changed the title chore(deps): update dependency sentry to v11 - autoclosed chore(deps): update dependency sentry to v11 Jul 31, 2025
@renovate renovate bot reopened this Jul 31, 2025
@renovate renovate bot force-pushed the renovate/sentry-11.x branch from 6870918 to d15d1da Compare July 31, 2025 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants