chore(deps): bump sentry from 0.47.0 to 0.48.2 in /crates

[dependabot]

Bumps sentry from 0.47.0 to 0.48.2.

Release notes

Sourced from sentry's releases.

0.48.2

New Features

• Added rustls-no-provider feature flag in the sentry crate to allow using the rustls transport with a different crypto provider (#1103).

Fixes

• Serialize attachment envelope headers as JSON to correctly encode header values (#1109).
• Use checked arithmetic to handle possible overflows (#1119, #1121, #1122).

0.48.1

Fixes

• Changed ClientOptions::enable_metrics to default to true, aligning metrics behavior with other Sentry SDKs (#1106). Metric capture APIs still require the metrics feature flag at compile time.

0.48.0

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;
let _guard = sentry::init((
"(your DSN here)",
ClientOptions {
enable_metrics: true,
// ... other options ...
..Default::default()
},
));

You can then capture metrics as follows:

</tr></table> 

... (truncated)

Changelog

Sourced from sentry's changelog.

0.48.2

New Features

• Added rustls-no-provider feature flag in the sentry crate to allow using the rustls transport with a different crypto provider (#1103).

Fixes

• Serialize attachment envelope headers as JSON to correctly encode header values (#1109).
• Use checked arithmetic to handle possible overflows (#1119, #1121, #1122).

0.48.1

Fixes

• Changed ClientOptions::enable_metrics to default to true, aligning metrics behavior with other Sentry SDKs (#1106). Metric capture APIs still require the metrics feature flag at compile time.

0.48.0

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;
let _guard = sentry::init((
"(your DSN here)",
ClientOptions {
enable_metrics: true,
// ... other options ...
..Default::default()
},
));

... (truncated)

Commits

• 8d8e8fc meta(changelog): Update CHANGELOG for version 0.48.2
• 3899506 release: 0.48.2
• a9fc8af fix(types): Use checked arithmetic in envelope parsing (#1122)
• a6ce8b0 feat: introduce rustls-no-provider feature flag (#1103)
• df88275 fix(ratelimit): Fix clippy::arithmetic_side_effects lint (#1121)
• d65272b fix: Enable clippy::arithmetic_side_effects lint (#1119)
• f801a2c build(deps): bump openssl from 0.10.78 to 0.10.79 (#1120)
• 5dc48f3 chore(meta): Centralize workspace lint config (#1114)
• 09aceec ref(sentry-panic): PanicInfo → PanicHookInfo (#1074)
• 2bebbd4 fix(types): Serialize attachment headers as JSON (#1109)
• Additional commits viewable in compare view