fix(deps): update sentry-rust to 0.48.0 by renovate[bot] · Pull Request #278 · arkedge/hubhook

renovate · 2024-11-29T10:52:54Z

This PR contains the following updates:

Package	Type	Update	Change
sentry (source)	dependencies	minor	`0.34.0` → `0.48.0`
sentry-actix (source)	dependencies	minor	`0.34.0` → `0.48.0`

Release Notes

getsentry/sentry-rust (sentry)

`v0.48.5`

Compare Source

Fixes

Fixed a bug that could cause the SDK to panic and, in some cases, panic while handling the panic, aborting the process (#1241).

`v0.48.4`

Compare Source

New Features

Added builder-style setters to ClientOptions (#1221):

// Before
let options = sentry::ClientOptions {
    dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
    debug: true,
    release: Some("my-app@1.0.0".into()),
    ..Default::default()
};

// After
let options = sentry::ClientOptions::new()
    .dsn("https://examplePublicKey@o0.ingest.sentry.io/0")
    .debug(true)
    .release("my-app@1.0.0");

Deprecations

Constructing ClientOptions with struct-literal syntax, including ..Default::default() functional update syntax, is deprecated and will stop compiling in the next breaking release, as we will mark ClientOptions as #[non_exhaustive] (#1221). Reading and assigning individual public fields will remain supported. Please migrate to the builder-style setters introduced in this release.

`v0.48.3`

Compare Source

The Sentry Rust SDK now reports data discarded by the SDK to Sentry’s Stats page. The SDK reports approximate counts for drops from transports, queues, rate-limit backoff, sampling, event processors, and before_send* callbacks, including span counts for dropped transactions and byte counts for dropped logs and metrics.

New Features

Added EnvelopeFilter and EnvelopeFilterCallbacks, which let callers observe envelope items removed by Envelope::filter, including attachments removed after their event or transaction is filtered out. Existing Envelope::filter closure callers continue to work, although some closures may require an explicit item type annotation (#1182).
Added the LossSource trait, which provides the client report data categories and quantities to report when supported Sentry data is dropped (#1170).
Added TransportFactory::create_transport_with_options, which constructs transports from TransportOptions instead of full ClientOptions (#1142).
Added transport-specific options types and with_options constructors for built-in HTTP transports, including ReqwestHttpTransportOptions, CurlHttpTransportOptions, UreqHttpTransportOptions, and EmbeddedSVCHttpTransportOptions (#1142).
Added transport worker options types and deprecated the legacy constructors for built-in background transport workers, including StdTransportThreadOptions and TokioTransportThreadOptions (#1142).
Added client report protocol types in sentry-types, including ClientReport, client_report::Item, client_report::Category, and client_report::Reason, plus support for serializing client_report envelope items (#1144).
Added a client report Recorder type, which modern TransportFactory implementations receive via TransportOptions. Transports can use this recorder to record discarded Sentry data; the SDK aggregates these reported losses and automatically sends them in a future envelope (#1158).

Deprecations

Deprecated Hub::with. Use Hub::current instead (#1126).

Fixes

Fixed ureq transport handling for HTTP error statuses so 429 rate limits and 413 payload-too-large responses are processed correctly (#1177).

Behavior Changes

Custom transport factories that implement TransportFactory::create_transport now receive ClientOptions reconstructed from TransportOptions. The reconstructed options include only transport-relevant fields, such as DSN, user agent, proxy settings, and TLS certificate validation settings. This may affect code that reads non-transport fields in create_transport, but the API remains source-compatible and this change is included in a minor/patch release (#1142).

`v0.48.2`

Compare Source

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).

`v0.48.1`

Compare Source

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.

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

`v0.47.0`

Compare Source

Breaking Changes

Update reqwest from 0.12.25 to 0.13.1 (#998). This change is breaking for users who use the RequestHttpTransport::with_client method.
sentry_core::HubSwitchGuard is now !Send, preventing it from being moved across threads (#957).

New Features

Added a Envelope::into_items method, which returns an iterator over owned EnvelopeItems in the Envelope (#983).
Expose transport utilities (#949)

Fixes

Fixed thread corruption bug where HubSwitchGuard could be dropped on wrong thread (#957).
We now fork the Hub every time a span is entered. This prevents data from leaking across spans (#957).

`v0.46.2`

Compare Source

New Features

Log HTTP 413 responses as oversized envelope discards in HTTP transports (#966)

Minimum Supported Rust Version

Bump minimum supported Rust version to 1.88 (#970).

`v0.46.1`

Compare Source

Improvements

Make it possible to == Transaction/Span/TransactionOrSpan (#942)

Dependencies

Update reqwest from 0.12.15 to 0.12.25 (#951)

`v0.46.0`

Compare Source

Breaking changes

Removed the ClientOptions struct's trim_backtraces and extra_border_frames fields (#925).
- These fields configured backtrace trimming, which is being removed in this release.

Improvements

Removed backtrace trimming to align the Rust SDK with the general principle that Sentry SDKs should only truncate telemetry data when needed to comply with documented size limits (#925). This change ensures that as much data as possible remains available for debugging.
- If you notice any new issues being created for existing errors after this change, please open an issue on GitHub.

Fixes

fix: adjust sentry.origin for log integration (#919) by @lcian

`v0.45.0`

Compare Source

Breaking changes

Add custom variant to AttachmentType that holds an arbitrary String. (#916)

`v0.44.0`

Compare Source

Breaking changes

feat(log): support combined LogFilters and RecordMappings (#914) by @lcian
- Breaking change: sentry::integrations::log::LogFilter has been changed to a bitflags struct.
- It's now possible to map a log record to multiple items in Sentry by combining multiple log filters in the filter, e.g. log::Level::ERROR => LogFilter::Event | LogFilter::Log.
- If using a custom mapper instead, it's possible to return a Vec<sentry::integrations::log::RecordMapping> to map a log record to multiple items in Sentry.

Behavioral changes

ref(log): send logs by default when logs feature flag is enabled (#915) by @lcian
- If the logs feature flag is enabled, the default Sentry log logger now sends logs for all events at or above INFO.
ref(logs): enable logs by default if logs feature flag is used (#910) by @lcian
- This changes the default value of sentry::ClientOptions::enable_logs to true.
- This simplifies the setup of Sentry structured logs by requiring users to just add the log feature flag to the sentry dependency to opt-in to sending logs.
- When the log feature flag is enabled, the tracing and log integrations will send structured logs to Sentry for all logs/events at or above INFO level by default.

`v0.43.0`

Compare Source

Breaking changes

ref(tracing): rework tracing to Sentry span name/op conversion (#887) by @lcian
- The tracing integration now uses the tracing span name as the Sentry span name by default.
- Before this change, the span name would be set based on the tracing span target (<module>::<function> when using the tracing::instrument macro).
- The tracing integration now uses <span target>::<span name> as the default Sentry span op (i.e. <module>::<function> when using tracing::instrument).
- Before this change, the span op would be set based on the tracing span name.
- Read below to learn how to customize the span name and op.
- When upgrading, please ensure to adapt any queries, metrics or dashboards to use the new span names/ops.
ref(tracing): use standard code attributes (#899) by @lcian
- Logs now carry the attributes code.module.name, code.file.path and code.line.number standardized in OTEL to surface the respective information, in contrast with the previously sent tracing.module_path, tracing.file and tracing.line.
fix(actix): capture only server errors (#877) by @lcian
- The Actix integration now properly honors the capture_server_errors option (enabled by default), capturing errors returned by middleware only if they are server errors (HTTP status code 5xx).
- Previously, if a middleware were to process the request after the Sentry middleware and return an error, our middleware would always capture it and send it to Sentry, regardless if it was a client, server or some other kind of error.
- With this change, we capture errors returned by middleware only if those errors can be classified as server errors.
- There is no change in behavior when it comes to errors returned by services, in which case the Sentry middleware only captures server errors exclusively.
fix: send trace origin correctly (#906) by @lcian
- TraceContext now has an additional field origin, used to report which integration created a transaction.

Behavioral changes

feat(tracing): send both breadcrumbs and logs by default (#878) by @lcian
- If the logs feature flag is enabled, and enable_logs: true is set on your client options, the default Sentry tracing layer now sends logs for all events at or above INFO.

Features

ref(tracing): rework tracing to Sentry span name/op conversion (#887) by @lcian
- Additional special fields have been added that allow overriding certain data on the Sentry span:
  - sentry.op: override the Sentry span op.
  - sentry.name: override the Sentry span name.
  - sentry.trace: given a string matching a valid sentry-trace header (sent automatically by client SDKs), continues the distributed trace instead of starting a new one. If the value is not a valid sentry-trace header or a trace is already started, this value is ignored.
- sentry.op and sentry.name can also be applied retroactively by declaring fields with value tracing::field::Empty and then recorded using tracing::Span::record.
- Example usage:
```
#[tracing::instrument(skip_all, fields(
    sentry.op = "http.server",
    sentry.name = "GET /payments",
    sentry.trace = headers.get("sentry-trace").unwrap_or(&"".to_owned()),
))]
async fn handle_request(headers: std::collections::HashMap<String, String>) {
    // ...
}
```
- Additional attributes are sent along with each span by default:
  - sentry.tracing.target: corresponds to the tracing span's metadata.target()
  - code.module.name, code.file.path, code.line.number

feat(core): add Response context (#874) by @lcian

The Response context can now be attached to events, to include information about HTTP responses such as headers, cookies and status code.

Example:

let mut event = Event::new();
let response = ResponseContext {
    cookies: Some(r#""csrftoken": "1234567""#.to_owned()),
    headers: Some(headers_map),
    status_code: Some(500),
    body_size: Some(15),
    data: Some("Invalid request"),
};
event
    .contexts
    .insert("response".to_owned(), response.into());

Fixes

build(panic): Fix build without other dependencies (#883) by @liskin
- The sentry-panic crate now builds successfully when used as a standalone dependency.
fix(transport): add rate limits for logs (#894) by @giortzisg

`v0.42.0`

Compare Source

Features

feat(log): support kv feature of log (#851) by @lcian
- Attributes added to a log record using the kv feature are now recorded as attributes on the log sent to Sentry.
feat(types): add all the missing supported envelope headers (#867) by @lcian
feat(types): add setters for envelope headers (#868) by @lcian
- It's now possible to set all of the envelope headers supported by the protocol when constructing envelopes.
feat(core): add some DSC fields to transaction envelope headers (#869) by @lcian
- The SDK now sends additional envelope headers with transactions. This should solve some extrapolation issues for span metrics.

Behavioral changes

feat: filter username and password in URLs (#864) by @lcian
- Usernames and passwords that could be contained in URLs captured when using the Actix Web or axum integration are now always filtered out.
- If the Request is created manually by the user, then these fields are not filtered out.
- This information was already filtered by Relay, but should also be filtered by the SDK itself as a first line of defense.

Fixes

docs: match description of debug option with behavior since PR #820 (#860) by @AlexTMjugador

`v0.41.0`

Compare Source

Breaking changes

feat(tracing): support combined EventFilters and EventMappings (#847) by @lcian
- EventFilter has been changed to a bitflags struct.
- It's now possible to map a tracing event to multiple items in Sentry by combining multiple event filters in the event_filter, e.g. tracing::Level::ERROR => EventFilter::Event | EventFilter::Log.
- It's also possible to use EventMapping::Combined to map a tracing event to multiple items in Sentry.
- ctx in the signatures of event_from_event, breadcrumb_from_event and log_from_event has been changed to take impl Into<Option<&'context Context<'context, S>>> to avoid cloning the Context when mapping to multiple items.

Features

feat(core): emit debug log when calling capture_log but logs are disabled (#849) by @lcian

Fixes

fix(logs): stringify u64 attributes greater than i64::MAX (#846) by @lcian

Dependencies

chore(deps): bump anyhow and disable its backtrace feature (#632) by @LunaBorowska

`v0.40.0`

Compare Source

Breaking changes

refactor(logs): apply user attributes to log regardless of send_default_pii (#843) by @lcian
- User attributes should be applied to logs regardless of send_default_pii. Therefore, that parameter was removed from sentry_core::Scope::apply_to_log.

Features

feat(tracing): add support for logs (#840) by @lcian
- To capture tracing events as Sentry structured logs, enable the logs feature of the sentry crate.
- Then, initialize the SDK with enable_logs: true in your client options.
- Finally, set up a custom event filter to map events to logs based on criteria such as severity. For example:
```
    let sentry_layer = sentry_tracing::layer().event_filter(|md| match *md.level() {
        tracing::Level::ERROR => EventFilter::Event,
        tracing::Level::TRACE => EventFilter::Ignore,
        _ => EventFilter::Log,
    });
```
feat(log): add support for logs (#841) by @lcian
- To capture log records as Sentry structured logs, enable the logs feature of the sentry crate.
- Then, initialize the SDK with enable_logs: true in your client options.
- Finally, set up a custom event filter to map records to Sentry logs based on criteria such as severity. For example:
```
    let logger = sentry::integrations::log::SentryLogger::new().filter(|md| match md.level() {
        log::Level::Error => LogFilter::Event,
        log::Level::Trace => LogFilter::Ignore,
        _ => LogFilter::Log,
    });
```
refactor(logs): cache default attributes and add OS attributes (#842) by @lcian
- os.name and os.version are now being attached to logs as default attributes.

Fixes

fix(logs): send environment in sentry.environment default attribute (#837) by @lcian

Behavioral changes

refactor(tracing): refactor internal code and improve docs (#839) by @lcian
- Errors carried by breadcrumbs will now be stored in the breadcrumb data under their original field name.
- Before, they were all stored under a single key called errors.

Dependencies

chore(deps): upgrade ureq to 3.x (#835) by @algesten

`v0.39.0`

Compare Source

Features

Support for Sentry structured logs has been added to the SDK.

To set up logs, enable the logs feature of the sentry crate and set enable_logs to true in your client options.
Then, use the logger_trace!, logger_debug!, logger_info!, logger_warn!, logger_error! and logger_fatal! macros to capture logs.
To filter or update logs before they are sent, you can use the before_send_log client option.
Please note that breaking changes could occur until the API is finalized.
feat(logs): add log protocol types (#821) by @lcian
feat(logs): add ability to capture and send logs (#823) by @lcian & @Swatinem
feat(logs): add macro-based API (#827) by @lcian & @szokeasaurusrex
feat(logs): send logs in batches (#831) by @lcian

Behavioral changes

feat(core): implement Tracing without Performance (#811) by @lcian
- The SDK now implements Tracing without Performance, which makes it so that each Scope is associated with an object holding some tracing information.
- This information is used as a fallback when capturing an event with tracing disabled or otherwise no ongoing span, to still allow related events to be linked by a trace.
- A new API Scope::iter_trace_propagation_headers has been provided that will use the fallback tracing information if there is no current Span on the Scope.

Breaking changes

refactor: remove debug-logs feature (#820) by @lcian
- The deprecated debug-logs feature of the sentry crate, used for the SDK's own internal logging, has been removed.

`v0.38.1`

Compare Source

Fixes

build: include sentry-actix optionally when release-health is enabled (#806) by @lcian
- sentry-actix is now being included as a dependency only when explicitly added, either as a direct dependency or through the actix feature flag of the sentry crate.
- Due to a mistake in the Cargo.toml, it was previously being included as a dependency by default when using just the sentry crate with default features.

`v0.38.0`

Compare Source

OpenTelemetry integration

An OpenTelemetry integration has been released. Please refer to the changelog entry below for the details.

Breaking changes

refactor(tracing): remove EventFilter::exception and always attach exception (#768) by @lcian
- The EventFilter::Exception enum variant has been removed. Please use EventFilter::Event instead to achieve the same behavior.
- Using EventFilter::Event will always attach any error struct used within the error field passed to the tracing macro, as EventFilter::Exception did previously.
- The error field will also be attached to breadcrumbs as an errors field resembling the structure of Sentry events created from error structs.
fix: use release-health flag in sentry-actix and remove it from subcrates where unneeded (#787) by @lcian
- As a follow-up from the changes in the previous release, the ClientOptions fields auto_session_tracking and session_mode are now gated behind the release-health feature flag of the sentry crate.
- If you depend on sentry with default-features = false, you need to include the release-health feature flag to benefit from the Release Health features of Sentry and have access to the aforementioned client options.
- The release-health feature flag is used correctly in sentry-actix to enable compilation of that subcrate when it's disabled.
- The release-health has been removed from the sentry-tracing and sentry-tower subcrates, where it was unnecessary.
refactor: remove Surf transport (#766) by @lcian
- The Surf transport has been removed as the surf crate is unmaintained and it was holding back dependency upgrades.
- If you really want to still use Surf, you can define a custom TransportFactory and pass it as the transport in your ClientOptions

Behavioral changes

refactor: honor send_default_pii in sentry-actix and sentry-tower (#771) by @lcian
- The client option send_default_pii (disabled by default) is now honored by sentry-actix and sentry-tower.
- This means that potentially sensitive headers such as authorization, cookies, and those that usually contain the user's IP address are filtered and not sent to Sentry.
- If you want to get back to the previous behavior and capture all headers, please set send_default_pii to true in your ClientOptions.
- Please refer to our Data Collected page for a comprehensive view of the data collected by the SDK.
refactor(debug-images): force init DEBUG_META on integration init (#773) by @lcian
- The DebugImages integration has been updated to init the DEBUG_META Lazy immediately.
- Using this integration is known to cause issues in specific versions of the Linux kernel due to issues in a library it depends on.
- Previously, on problematic systems the SDK would cause deadlock after capturing the first event. Now the SDK will panic on initialization instead. Please open an issue if you're affected.

Features

feat(otel): add OpenTelemetry SpanProcessor, Propagator, Extractor (#779) by @lcian
- A new integration for the opentelemetry crate has been released.
- It can be used to capture spans created using the opentelemetry API and send them to Sentry.
- Distributed tracing is also supported, provided that the upstream/downstream services support the Sentry or W3C distributed tracing metadata format.
- Please refer to the subcrate's README or the crate docs to see an example of setup and usage.
feat: expose sentry-actix as a feature of sentry (#788) by @lcian
- sentry-actix is now exposed by the sentry crate as sentry::integrations::actix, gated behind the actix feature flag.
- Please update your dependencies to not depend on the sentry-actix subcrate directly.

Dependencies

build(deps): bump openssl from 0.10.71 to 0.10.72 (#762) by @dependabot
build(deps): bump tokio from 1.44.1 to 1.44.2 (#763) by @dependabot
chore(deps): bump some dependencies and update Cargo.lock (#772) by @lcian

Various fixes & improvements

Replace once_cell with std::sync::LazyLock (#776) by @FalkWoldmann
chore: update GH issue templates for Linear compatibility (#777) by @stephanie-anderson
chore: update issue templates with blank issue and Discord link (#778) by @lcian
refactor(core): fail with message if TLS backend not available (#784) by @lcian
build: add sentry-opentelemetry to workspace (#789) by @lcian
docs: update docs including OTEL and other integrations (#790) by @lcian
fix(otel): fix doctests (#794) by @lcian
fix(otel): fix span and trace ids for distributed tracing (#801) by @lcian
build(otel): exclude version from circular dev-dependencies (#802) by @lcian

`v0.37.0`

Compare Source

Breaking changes

chore(msrv): cargo update and bump MSRV to 1.81 (#754) by @lcian
- The minimum supported Rust version has been raised to 1.81.
feat(core): introduce release-health feature (#749) by @pepperoni505
- A new release-health feature flag was introduced that gates the Release Health features of Sentry.
- This allows for compilation of the SDK on certain WASM targets.
- Release Health features were already present and enabled with no feature flag in previous versions.
- The new feature flag will be enabled by default when using sentry, sentry-actix, sentry-tower or sentry-tracing with the default features.
- If you're fine-tuning your feature flags, make sure to enable release-health to get back the previous behavior.
ref(metrics): remove features and code related to the old metrics beta (#740) by @lcian
- The metrics feature and the code related to it has been removed from the crate, as the Sentry backend stopped ingesting metrics a while ago.
Switch to MIT license (#724) by @cleptric
- The license for the crates has been changed to MIT.

Features

feat(actix): capture HTTP request body (#731) by @pacifistes
- The middleware for actix-web now supports capturing and attaching the request body to HTTP request transactions.
- You need to enable send_default_pii in your client options for this to be enabled, and you can fine-tune the behavior using the new option max_request_body_size.
feat(core): transaction.set_data sets data on TraceContext (#739) by @lcian
- transaction.set_data now sets data on TraceContext, as the SDK should not use the extra field.
ref(backtrace): add entries and extra logic for in-app detection (#756) by @lcian
feat(core): add more frames to be considered not in_app (#760) by @lcian
- The logic used by the SDK to detect in-app stack frames has been improved. Now the SDK will mark more frames as not in-app.
- A similar improvement has been added to the Sentry backend so that old versions of the SDK can benefit from improved in-app reporting.

Fixes

fix(http): Finish transaction on drop (#727) by @Dav1dde
- Fixed a bug where the current transaction was not finished (hence not sent to Sentry) when its corresponding future was dropped, e.g. due to a panic.
follow #439 for actix-web. fix #680 (#737) by @pavel-rosputko
- The HTTP request metadata is now being correctly attached to transactions when using sentry-actix.
fix(tracing): wrap error with synthetic mechanism only if attaching stacktrace (#755) by @lcian
- Fixed a bug that should result in improved grouping and issue titles for events reported by sentry-tracing when not capturing stack traces.
fix(actix): process request in other middleware using correct Hub (#758) by @lcian
- The subsequent middleware in the chain when processing a request now execute within the correct Hub.
fix(anyhow): attach stacktrace only if error provides backtrace (#759) by @lcian
- Fixed a bug where the SDK was providing incorrect stack traces when capturing an anyhow when the backtrace feature is enabled but RUST_BACKTRACE is not set.
- This should result in correct grouping of the affected issues.

Various fixes & improvements

Fix CS (#726) by @cleptric
fix(doctests): update prost (#750) by @lcian
chore(msrv): bump MSRV to 1.75 (#751) by @lcian
refactor(actix): simplify body_from_http (#757) by @robjtede
chore: prepare changelog for release (#761) by @lcian

Dependencies

build(deps): bump openssl from 0.10.66 to 0.10.70 (#732) by @dependabot
build(deps): bump ring from 0.17.8 to 0.17.13 (#747) by @dependabot

`v0.36.0`

Compare Source

Various fixes & improvements

feat(sentry-tower) Make SentryLayer and SentryService Sync if request isn't (#721) by @syphar
sentry-tower: Update axum dependency to v0.8 (#718) by @Turbo87
Allow retrieving user of scope (#715) by @thomaseizinger
Elide lifetimes where possible (#716) by @thomaseizinger
Replace release bot with GH app (#714) by @Jeffreyhung
Delay sampling of span to finish (#712) by @thomaseizinger

`v0.35.0`

Compare Source

Fixes:

Envelopes will be discarded rather than blocking if the transport channel fills up (previously fixed in async-capable transports, now applied to the curl/ureq transports). (#701)

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

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 these updates 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 Bot assigned sksat (sksat) Nov 29, 2024

renovate Bot requested a review from sksat (sksat) November 29, 2024 10:52

renovate Bot force-pushed the renovate/sentry branch from fc11361 to cd0dba2 Compare January 8, 2025 13:21

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.35.0~~ fix(deps): update sentry-rust to 0.36.0 Jan 8, 2025

renovate Bot force-pushed the renovate/sentry branch from cd0dba2 to 1998ef0 Compare April 1, 2025 14:30

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.36.0~~ fix(deps): update sentry-rust to 0.37.0 Apr 1, 2025

renovate Bot force-pushed the renovate/sentry branch from 1998ef0 to 0e2e632 Compare April 2, 2025 08:03

renovate Bot force-pushed the renovate/sentry branch from 0e2e632 to ea88003 Compare May 9, 2025 16:07

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.37.0~~ fix(deps): update sentry-rust to 0.38.0 May 9, 2025

renovate Bot force-pushed the renovate/sentry branch from ea88003 to 3bf1e30 Compare June 10, 2025 12:32

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.38.0~~ fix(deps): update sentry-rust to 0.39.0 Jun 10, 2025

renovate Bot force-pushed the renovate/sentry branch from 3bf1e30 to 5530fe1 Compare June 17, 2025 12:31

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.39.0~~ fix(deps): update sentry-rust to 0.40.0 Jun 17, 2025

renovate Bot force-pushed the renovate/sentry branch from 5530fe1 to 6f364e5 Compare June 23, 2025 14:32

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.40.0~~ fix(deps): update sentry-rust to 0.41.0 Jun 23, 2025

renovate Bot force-pushed the renovate/sentry branch from 6f364e5 to cba6f9e Compare July 29, 2025 12:45

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.41.0~~ fix(deps): update sentry-rust to 0.42.0 Jul 29, 2025

renovate Bot force-pushed the renovate/sentry branch from cba6f9e to 6346057 Compare August 10, 2025 14:22

renovate Bot force-pushed the renovate/sentry branch from 6346057 to 2c75717 Compare September 24, 2025 10:07

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.42.0~~ fix(deps): update sentry-rust to 0.43.0 Sep 24, 2025

renovate Bot force-pushed the renovate/sentry branch from 2c75717 to 8946825 Compare September 25, 2025 19:55

renovate Bot force-pushed the renovate/sentry branch from 8946825 to 818d22f Compare October 7, 2025 10:06

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.43.0~~ fix(deps): update sentry-rust to 0.44.0 Oct 7, 2025

renovate Bot force-pushed the renovate/sentry branch from 818d22f to 5cea7d6 Compare October 8, 2025 13:13

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.44.0~~ fix(deps): update sentry-rust to 0.45.0 Oct 8, 2025

renovate Bot force-pushed the renovate/sentry branch from 5cea7d6 to 730a72d Compare November 24, 2025 17:41

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.45.0~~ fix(deps): update sentry-rust to 0.46.0 Nov 24, 2025

renovate Bot force-pushed the renovate/sentry branch from 730a72d to 0c22452 Compare December 10, 2025 15:52

renovate Bot force-pushed the renovate/sentry branch 2 times, most recently from 5301416 to cde2b6f Compare January 7, 2026 09:52

renovate Bot force-pushed the renovate/sentry branch from cde2b6f to 62d4c02 Compare March 1, 2026 19:23

renovate Bot force-pushed the renovate/sentry branch from 62d4c02 to 5a26d9d Compare March 10, 2026 17:24

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.46.0~~ fix(deps): update sentry-rust to 0.47.0 Mar 10, 2026

renovate Bot force-pushed the renovate/sentry branch from 5a26d9d to a09d91e Compare March 13, 2026 18:40

renovate Bot changed the title ~~fix(deps): update sentry-rust to 0.47.0~~ fix(deps): update sentry-rust to 0.48.0 Apr 28, 2026

renovate Bot force-pushed the renovate/sentry branch 2 times, most recently from cdc6573 to 3be0f4c Compare May 4, 2026 15:47

renovate Bot force-pushed the renovate/sentry branch from 3be0f4c to b1a4983 Compare May 11, 2026 09:49

renovate Bot force-pushed the renovate/sentry branch from b1a4983 to 3afda69 Compare May 18, 2026 18:54

renovate Bot force-pushed the renovate/sentry branch from 3afda69 to a78b306 Compare June 25, 2026 10:12

renovate Bot force-pushed the renovate/sentry branch from a78b306 to ae004e4 Compare July 7, 2026 10:01

fix(deps): update sentry-rust to 0.48.0

efdfcc6

renovate Bot force-pushed the renovate/sentry branch from ae004e4 to efdfcc6 Compare July 14, 2026 09:50

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update sentry-rust to 0.48.0#278

fix(deps): update sentry-rust to 0.48.0#278
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/sentry

renovate Bot commented Nov 29, 2024 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

renovate Bot commented Nov 29, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Fixes

New Features

Deprecations

New Features

Deprecations

Fixes

Behavior Changes

New Features

Fixes

Fixes

Breaking Changes

New Features

Fixes

Breaking Changes

New Features

Fixes

New Features

Minimum Supported Rust Version

Improvements

Dependencies

Breaking changes

Improvements

Fixes

Breaking changes

Breaking changes

Behavioral changes

Breaking changes

Behavioral changes

Features

Fixes

Features

Behavioral changes

Fixes

Breaking changes

Features

Fixes

Dependencies

Breaking changes

Features

Fixes

Behavioral changes

Dependencies

Features

Behavioral changes

Breaking changes

Fixes

OpenTelemetry integration

Breaking changes

Behavioral changes

Features

Dependencies

Various fixes & improvements

Breaking changes

Features

Fixes

Various fixes & improvements

Dependencies

Various fixes & improvements

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate Bot commented Nov 29, 2024 •

edited

Loading