fix(deps): update rust crate sentry to 0.48.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Pending
sentry (source)	dependencies	minor	0.47.0 → 0.48.0	0.48.1

---

Release Notes

getsentry/sentry-rust (sentry)

v0.48.0

Compare Source

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:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;

// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
    .unit(Unit::Millisecond) // units can also be set on gauges
    .attribute("http.status", 200) // attributes can be set on all metric types
    .capture();

Fixes

• Fixed several feature additivity SemVer violations, where enabling a feature flag could have introduced breaking changes. All known violations are fixed now, so simply enabling an additional feature flag in any Sentry SDK crate should no longer cause any public API breakages. Fixing these issues required us to break the public API in some places; those breakages are detailed above.

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • "before 3am"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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]

⚠️ 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: Cargo.toml

Artifact update for sentry resolved to version 0.48.1, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 0.48.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/