feat: Update Sentry to v0.35 (#14)

Author: timfish

Cargo.toml

@@ -5,19 +5,19 @@ license = "MIT OR Apache-2.0"
 name = "sentry-rust-minidump"
 readme = "README.md"
 repository = "https://github.com/timfish/sentry-rust-minidump"
-version = "0.8.0"
+version = "0.9.0"
 
 [dependencies]
 minidumper-child = "0.2"
-sentry = "0.34"
-thiserror = "1"
+sentry = "0.35"
+thiserror = "2"
 serde = { version = "1", features = ["derive"], optional = true }
 serde_json = { version = "1", optional = true }
 
 [dev-dependencies]
 actix-rt = "2.7"
-sadness-generator = "0.5"
-sentry-test-server = {git = "https://github.com/timfish/sentry-test-server.git", rev = "3845172"}
+sadness-generator = "0.6"
+sentry-test-server = {git = "https://github.com/timfish/sentry-test-server.git", rev = "4d53bfe"}
 
 [features]
 ipc = [ "dep:serde", "dep:serde_json"]

README.md

@@ -1,25 +1,25 @@
-# `sentry-rust-minidump` 
+# `sentry-rust-minidump`
 
 ![Master branch integration test status](https://img.shields.io/github/actions/workflow/status/timfish/sentry-rust-minidump/test.yml?label=Integration%20Tests&style=for-the-badge)
 
 Uses the [`minidumper-child`](https://github.com/timfish/minidumper-child) crate
 to capture minidumps from a separate process and sends them to Sentry as
-attachments via the Sentry Rust SDK. 
+attachments via the Sentry Rust SDK.
 
-`sentry_rust_minidump::init` starts the current executable again with an argument that
-causes it to start in crash reporter mode. In this mode it waits for minidump
-notification from the main app process and handles writing and sending of the
-minidump file as an attachment to Sentry.
+`sentry_rust_minidump::init` starts the current executable again with an
+argument that causes it to start in crash reporter mode. In this mode it waits
+for minidump notification from the main app process and handles writing and
+sending of the minidump file as an attachment to Sentry.
 
 Everything before `sentry_rust_minidump::init` is called in both the main and
-crash reporter processes and should configure and start Sentry. Everything
-after `sentry_rust_minidump::init` is only called in the main process to run
-your application code.
+crash reporter processes and should configure and start Sentry. Everything after
+`sentry_rust_minidump::init` is only called in the main process to run your
+application code.
 
 ```toml
 [dependencies]
-sentry = "0.34"
-sentry-rust-minidump = "0.8"
+sentry = "0.35"
+sentry-rust-minidump = "0.9"
 ```
 
 ```rust
@@ -44,7 +44,7 @@ fn main() {
 
 By default there is no scope synchronisation from the app process to the crash
 reporter process. This means that native crash event will be missing
-breadcrumbs, user, tags or extra added to the scope in the app.  
+breadcrumbs, user, tags or extra added to the scope in the app.
 
 When the `ipc` feature is enabled, you can send scope updates to the crash
 reporter process:
@@ -64,4 +64,4 @@ fn main() {
 
     // Don't drop crash_reporter or the reporter process will close!
 }
-```
+```