release: 0.37.0

getsentry-bot · getsentry-bot · commit 7e6d8cbd5e31 · 2025-04-01T10:53:55.000Z
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,6 +1,6 @@
 # Changelog
 
-## Unreleased
+## 0.37.0
 
 ### Breaking changes
 
@@ -56,7 +56,6 @@
 - 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
 
-
 ## 0.36.0
 
 ### Various fixes & improvements
diff --git a/sentry-actix/Cargo.toml b/sentry-actix/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-actix"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -20,7 +20,7 @@ release-health = ["sentry-core/release-health"]
 actix-web = { version = "4", default-features = false }
 bytes = "1.2"
 futures-util = { version = "0.3.5", default-features = false }
-sentry-core = { version = "0.36.0", path = "../sentry-core", default-features = false, features = [
+sentry-core = { version = "0.37.0", path = "../sentry-core", default-features = false, features = [
     "client",
 ] }
 actix-http = "3.10"
diff --git a/sentry-actix/README.md b/sentry-actix/README.md
@@ -11,8 +11,7 @@ report them to `Sentry`.
 
 To use this middleware just configure Sentry and then add it to your actix web app as a
 middleware.  Because actix is generally working with non sendable objects and highly concurrent
-this middleware creates a new hub per request.  As a result many of the sentry integrations
-such as breadcrumbs do not work unless you bind the actix hub.
+this middleware creates a new Hub per request.
 
 ## Example
 
@@ -67,12 +66,16 @@ let _sentry = sentry::init(sentry::ClientOptions {
 ## Reusing the Hub
 
 This integration will automatically create a new per-request Hub from the main Hub, and update the
-current Hub instance. For example, the following will capture a message in the current request's Hub:
+current Hub instance. For example, the following in the handler or in any of the subsequent
+middleware will capture a message in the current request's Hub:
 
 ```rust
 sentry::capture_message("Something is not well", sentry::Level::Warning);
 ```
 
+It is recommended to register the Sentry middleware as the last, i.e. the first to be executed
+when processing a request, so that the rest of the processing will run with the correct Hub.
+
 ## Resources
 
 License: MIT
diff --git a/sentry-anyhow/Cargo.toml b/sentry-anyhow/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-anyhow"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -17,8 +17,8 @@ default = ["backtrace"]
 backtrace = ["anyhow/backtrace"]
 
 [dependencies]
-sentry-backtrace = { version = "0.36.0", path = "../sentry-backtrace" }
-sentry-core = { version = "0.36.0", path = "../sentry-core" }
+sentry-backtrace = { version = "0.37.0", path = "../sentry-backtrace" }
+sentry-core = { version = "0.37.0", path = "../sentry-core" }
 anyhow = "1.0.39"
 
 [dev-dependencies]
diff --git a/sentry-backtrace/Cargo.toml b/sentry-backtrace/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-backtrace"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -19,4 +19,4 @@ regex = { version = "1.5.5", default-features = false, features = [
     "std",
     "unicode-perl",
 ] }
-sentry-core = { version = "0.36.0", path = "../sentry-core" }
+sentry-core = { version = "0.37.0", path = "../sentry-core" }
diff --git a/sentry-contexts/Cargo.toml b/sentry-contexts/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-contexts"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -14,7 +14,7 @@ edition = "2021"
 rust-version = "1.81"
 
 [dependencies]
-sentry-core = { version = "0.36.0", path = "../sentry-core" }
+sentry-core = { version = "0.37.0", path = "../sentry-core" }
 libc = "0.2.66"
 hostname = "0.4"
 
diff --git a/sentry-core/Cargo.toml b/sentry-core/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-core"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -35,7 +35,7 @@ log = { version = "0.4.8", optional = true, features = ["std"] }
 once_cell = "1"
 rand = { version = "0.8.1", optional = true }
 regex = { version = "1.7.3", optional = true }
-sentry-types = { version = "0.36.0", path = "../sentry-types" }
+sentry-types = { version = "0.37.0", path = "../sentry-types" }
 serde = { version = "1.0.104", features = ["derive"] }
 serde_json = { version = "1.0.46" }
 uuid = { version = "1.0.0", features = ["v4", "serde"], optional = true }
diff --git a/sentry-core/README.md b/sentry-core/README.md
@@ -102,7 +102,7 @@ functionality.
 [Sentry]: https://sentry.io/
 [`sentry`]: https://crates.io/crates/sentry
 [Unified API]: https://develop.sentry.dev/sdk/unified-api/
-[`test`]: https://docs.rs/sentry-core/0.36.0/sentry_core/test/index.html
+[`test`]: https://docs.rs/sentry-core/0.37.0/sentry_core/test/index.html
 
 ## Resources
 
diff --git a/sentry-debug-images/Cargo.toml b/sentry-debug-images/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-debug-images"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -15,4 +15,4 @@ rust-version = "1.81"
 [dependencies]
 findshlibs = "=0.10.2"
 once_cell = "1"
-sentry-core = { version = "0.36.0", path = "../sentry-core" }
+sentry-core = { version = "0.37.0", path = "../sentry-core" }
diff --git a/sentry-debug-images/README.md b/sentry-debug-images/README.md
@@ -22,7 +22,7 @@ let integration = sentry_debug_images::DebugImagesIntegration::new()
     .filter(|event| event.level >= Level::Warning);
 ```
 
-[`Event`]: https://docs.rs/sentry-debug-images/0.36.0/sentry_debug_images/sentry_core::protocol::Event
+[`Event`]: https://docs.rs/sentry-debug-images/0.37.0/sentry_debug_images/sentry_core::protocol::Event
 
 ## Resources
 
diff --git a/sentry-log/Cargo.toml b/sentry-log/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-log"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -13,7 +13,7 @@ edition = "2021"
 rust-version = "1.81"
 
 [dependencies]
-sentry-core = { version = "0.36.0", path = "../sentry-core" }
+sentry-core = { version = "0.37.0", path = "../sentry-core" }
 log = { version = "0.4.8", features = ["std"] }
 
 [dev-dependencies]
diff --git a/sentry-panic/Cargo.toml b/sentry-panic/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-panic"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -13,8 +13,8 @@ edition = "2021"
 rust-version = "1.81"
 
 [dependencies]
-sentry-core = { version = "0.36.0", path = "../sentry-core" }
-sentry-backtrace = { version = "0.36.0", path = "../sentry-backtrace" }
+sentry-core = { version = "0.37.0", path = "../sentry-core" }
+sentry-backtrace = { version = "0.37.0", path = "../sentry-backtrace" }
 
 [dev-dependencies]
 sentry = { path = "../sentry", default-features = false, features = ["test"] }
diff --git a/sentry-slog/Cargo.toml b/sentry-slog/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-slog"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -13,7 +13,7 @@ edition = "2021"
 rust-version = "1.81"
 
 [dependencies]
-sentry-core = { version = "0.36.0", path = "../sentry-core" }
+sentry-core = { version = "0.37.0", path = "../sentry-core" }
 slog = { version = "2.5.2", features = ["nested-values"] }
 serde_json = "1.0.46"
 
diff --git a/sentry-tower/Cargo.toml b/sentry-tower/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-tower"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -27,7 +27,7 @@ tower-layer = "0.3"
 tower-service = "0.3"
 http = { version = "1.0.0", optional = true }
 pin-project = { version = "1.0.10", optional = true }
-sentry-core = { version = "0.36.0", path = "../sentry-core", default-features = false, features = [
+sentry-core = { version = "0.37.0", path = "../sentry-core", default-features = false, features = [
     "client",
 ] }
 url = { version = "2.2.2", optional = true }
diff --git a/sentry-tower/README.md b/sentry-tower/README.md
@@ -103,7 +103,7 @@ feature of the `sentry` crate instead of the `tower` feature.
 The created transaction will automatically use the request URI as its name.
 This is sometimes not desirable in case the request URI contains unique IDs
 or similar. In this case, users should manually override the transaction name
-in the request handler using the [`Scope::set_transaction`](https://docs.rs/sentry-tower/0.36.0/sentry_tower/sentry_core::Scope::set_transaction)
+in the request handler using the [`Scope::set_transaction`](https://docs.rs/sentry-tower/0.37.0/sentry_tower/sentry_core::Scope::set_transaction)
 method.
 
 When combining both layers, take care of the ordering of both. For example
diff --git a/sentry-tracing/Cargo.toml b/sentry-tracing/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-tracing"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -21,14 +21,14 @@ backtrace = ["dep:sentry-backtrace"]
 release-health = ["sentry-core/release-health"]
 
 [dependencies]
-sentry-core = { version = "0.36.0", path = "../sentry-core", features = [
+sentry-core = { version = "0.37.0", path = "../sentry-core", features = [
     "client",
 ] }
 tracing-core = "0.1"
 tracing-subscriber = { version = "0.3.1", default-features = false, features = [
     "std",
 ] }
-sentry-backtrace = { version = "0.36.0", path = "../sentry-backtrace", optional = true }
+sentry-backtrace = { version = "0.37.0", path = "../sentry-backtrace", optional = true }
 
 [dev-dependencies]
 log = "0.4"
diff --git a/sentry-tracing/README.md b/sentry-tracing/README.md
@@ -83,7 +83,7 @@ tracing::error!(
 );
 ```
 
-To track [error structs](https://docs.rs/sentry-tracing/0.36.0/sentry_tracing/std::error::Error), assign a reference to error trait object as field
+To track [error structs](https://docs.rs/sentry-tracing/0.37.0/sentry_tracing/std::error::Error), assign a reference to error trait object as field
 in one of the logging macros. By convention, it is recommended to use the `ERROR` level and
 assign it to a field called `error`, although the integration will also work with all other
 levels and field names.
diff --git a/sentry-types/Cargo.toml b/sentry-types/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry-types"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
diff --git a/sentry/Cargo.toml b/sentry/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "sentry"
-version = "0.36.0"
+version = "0.37.0"
 authors = ["Sentry <hello@sentry.io>"]
 license = "MIT"
 readme = "README.md"
@@ -60,18 +60,18 @@ rustls = ["dep:rustls", "reqwest?/rustls-tls", "ureq?/tls", "webpki-roots"]
 embedded-svc-http = ["dep:embedded-svc", "dep:esp-idf-svc"]
 
 [dependencies]
-sentry-core = { version = "0.36.0", path = "../sentry-core", features = [
+sentry-core = { version = "0.37.0", path = "../sentry-core", features = [
     "client",
 ] }
-sentry-anyhow = { version = "0.36.0", path = "../sentry-anyhow", optional = true }
-sentry-backtrace = { version = "0.36.0", path = "../sentry-backtrace", optional = true }
-sentry-contexts = { version = "0.36.0", path = "../sentry-contexts", optional = true }
-sentry-debug-images = { version = "0.36.0", path = "../sentry-debug-images", optional = true }
-sentry-log = { version = "0.36.0", path = "../sentry-log", optional = true }
-sentry-panic = { version = "0.36.0", path = "../sentry-panic", optional = true }
-sentry-slog = { version = "0.36.0", path = "../sentry-slog", optional = true }
-sentry-tower = { version = "0.36.0", path = "../sentry-tower", optional = true }
-sentry-tracing = { version = "0.36.0", path = "../sentry-tracing", optional = true }
+sentry-anyhow = { version = "0.37.0", path = "../sentry-anyhow", optional = true }
+sentry-backtrace = { version = "0.37.0", path = "../sentry-backtrace", optional = true }
+sentry-contexts = { version = "0.37.0", path = "../sentry-contexts", optional = true }
+sentry-debug-images = { version = "0.37.0", path = "../sentry-debug-images", optional = true }
+sentry-log = { version = "0.37.0", path = "../sentry-log", optional = true }
+sentry-panic = { version = "0.37.0", path = "../sentry-panic", optional = true }
+sentry-slog = { version = "0.37.0", path = "../sentry-slog", optional = true }
+sentry-tower = { version = "0.37.0", path = "../sentry-tower", optional = true }
+sentry-tracing = { version = "0.37.0", path = "../sentry-tracing", optional = true }
 log = { version = "0.4.8", optional = true, features = ["std"] }
 reqwest = { version = "0.12", optional = true, features = [
     "blocking",
diff --git a/sentry/README.md b/sentry/README.md
@@ -34,8 +34,8 @@ sentry::capture_message("Hello World!", sentry::Level::Info);
 More complex examples on how to use sentry can also be found in [examples]. Extended instructions
 may also be found on [Sentry itself].
 
-[`sentry::init`]: https://docs.rs/sentry/0.36.0/sentry/fn.init.html
-[`Hub`]: https://docs.rs/sentry/0.36.0/sentry/struct.Hub.html
+[`sentry::init`]: https://docs.rs/sentry/0.37.0/sentry/fn.init.html
+[`Hub`]: https://docs.rs/sentry/0.37.0/sentry/struct.Hub.html
 [examples]: https://github.com/getsentry/sentry-rust/tree/master/sentry/examples
 [Sentry itself]: https://docs.sentry.io/platforms/rust
 
@@ -47,17 +47,17 @@ the ecosystem require a feature flag. For available integrations and how to use
 [integrations] and [apply_defaults].
 
 [Features]: #features
-[integrations]: https://docs.rs/sentry/0.36.0/sentry/integrations/index.html
-[apply_defaults]: https://docs.rs/sentry/0.36.0/sentry/fn.apply_defaults.html
+[integrations]: https://docs.rs/sentry/0.37.0/sentry/integrations/index.html
+[apply_defaults]: https://docs.rs/sentry/0.37.0/sentry/fn.apply_defaults.html
 
 ## Minimal API
 
 This crate comes fully-featured. If the goal is to instrument libraries for usage
 with sentry, or to extend sentry with a custom [`Integration`] or a [`Transport`],
 one should use the [`sentry-core`] crate instead.
 
-[`Integration`]: https://docs.rs/sentry/0.36.0/sentry/trait.Integration.html
-[`Transport`]: https://docs.rs/sentry/0.36.0/sentry/trait.Transport.html
+[`Integration`]: https://docs.rs/sentry/0.37.0/sentry/trait.Integration.html
+[`Transport`]: https://docs.rs/sentry/0.37.0/sentry/trait.Transport.html
 [`sentry-core`]: https://crates.io/crates/sentry-core
 
 ## Features
