sentry breaking changes

0.49.0

11 breaking changes, first published July 29, 2026.

• Removed ClientOptions.sample_rate
  The public sample_rate field is gone. Inspect the configured strategy with event_sampling_strategy, and use the sample_rate(...) builder setter to configure fixed-rate sampling. github.com
• Removed ClientOptions.traces_sample_rate
  The public traces_sample_rate field is gone. Inspect the configured strategy with traces_sampling_strategy, and use the traces_sample_rate(...) builder setter instead. github.com
• Removed ClientOptions.traces_sampler
  The public traces_sampler field is gone. Inspect the configured strategy with traces_sampling_strategy, and use the traces_sampler(...) builder setter instead. github.com
• Behavior changed
  The sentry-opentelemetry integration now supports OpenTelemetry 0.32. Users must update their OpenTelemetry dependencies from 0.29 to 0.32. github.com
• Default changed
  The logs and metrics features are enabled by default in the sentry crate, so new telemetry may be sent. Disable these features explicitly if that telemetry is not wanted. github.com
• Signature changed ClientOptions
  ClientOptions can no longer be built with a struct literal. Construct it with ClientOptions::new() and the builder-style setters instead. github.com
• Signature changed EnvelopeError
  EnvelopeError is now non-exhaustive, so matches on its variants need a wildcard arm. github.com
• Signature changed EnvelopeItem
  The Event and Transaction variants now hold Box values. Code that constructs or matches these variants must account for the extra indirection. github.com
• Signature changed sentry_log.RecordMapping
  The Event variant of RecordMapping now stores the event in a Box. Code that constructs or matches it must be updated. github.com
• Signature changed sentry_slog.RecordMapping
  RecordMapping is now non-exhaustive, so matches need a wildcard arm. Its Event variant now stores a boxed Event. github.com

And 1 more in this version.

Check your code

These are the changes. To see which of them reach your code, scan a public repository, or have your coding agent call check_code with your manifest or lockfile over MCP. The API reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.