docs: update Rust SDK docs for posthog-rs v0.14 (fire-and-forget capture)

contents/docs/experiments/installation/rust.mdx

@@ -30,7 +30,7 @@ For this tutorial, let's report a conversion event when a user clicks a CTA. In
 use posthog_rs::Event;
 
 let event = Event::new("cta clicked", "user_distinct_id");
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 </Step>

contents/docs/getting-started/_snippets/user-properties-how-to-set.mdx

@@ -100,7 +100,7 @@ let mut set_once = HashMap::new();
 set_once.insert("initial_url", "/blog");
 event.insert_prop("$set_once", set_once).unwrap();
 
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 ```bash

contents/docs/integrate/_snippets/install-rust.mdx

@@ -2,7 +2,7 @@ Install the `posthog-rs` crate by adding it to your `Cargo.toml`.
 
 ```toml file=Cargo.toml
 [dependencies]
-posthog-rs = "0.13.1"
+posthog-rs = "0.14"
 ```
 
 Next, set up the client with your PostHog project key.
@@ -19,7 +19,7 @@ If you need to use a synchronous client instead – like we do in our [CLI](http
 
 ```toml
 [dependencies]
-posthog-rs = { version = "0.13.1", default-features = false }
+posthog-rs = { version = "0.14", default-features = false }
 ```
 
-In blocking mode, calls to `capture` and related methods will block until the PostHog event capture API returns – generally this is on the order of tens of milliseconds, but you may want to `thread::spawn` a background thread when you send an event.
+With the blocking client, the same methods are available without `.await`. Either way, `capture` is non-blocking: it hands the event to a background worker that batches and sends it, so it returns immediately instead of waiting on the network. Because delivery happens in the background, call `flush()` or `shutdown()` before your program exits, or buffered events may be lost.

contents/docs/integrate/feature-flags-code/_snippets/feature-flags-code-rust.mdx

@@ -69,7 +69,7 @@ if flags.is_enabled("flag-key") {
 
 let mut event = Event::new("event_name", "distinct_id_of_your_user");
 event.with_flags(&flags);
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 By default, this attaches every flag in the snapshot using `$feature/<flag-key>` properties and `$active_feature_flags`.
@@ -80,12 +80,12 @@ To reduce event property bloat, pass a filtered snapshot:
 // Attach only flags accessed with is_enabled() or get_flag() before this call
 let mut event = Event::new("event_name", "distinct_id_of_your_user");
 event.with_flags(&flags.only_accessed());
-client.capture(event).await.unwrap();
+client.capture(event);
 
 // Attach only specific flags
 let mut event = Event::new("event_name", "distinct_id_of_your_user");
 event.with_flags(&flags.only(&["checkout-flow", "new-dashboard"]));
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 `only_accessed()` is order-dependent. If you call it before accessing any flags with `is_enabled()` or `get_flag()`, no feature flag properties are attached.
@@ -99,7 +99,7 @@ use posthog_rs::Event;
 
 let mut event = Event::new("event_name", "distinct_id_of_your_user");
 event.insert_prop("$feature/feature-flag-key", "variant-key").unwrap();
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 ### Evaluating only specific flags

contents/docs/integrate/send-events/_snippets/send-events-rust.mdx

@@ -6,7 +6,7 @@ import Intro from "./intro.mdx"
 
 ```rust
 let mut event = Event::new("user_signed_up", "distinct_id_of_the_user");
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 <NamingTip />
@@ -19,7 +19,7 @@ let mut event = Event::new("user_signed_up", "distinct_id_of_the_user");
 event.insert_prop("login_type", "email").unwrap();
 event.insert_prop("is_free_trial", true).unwrap();
 
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 ### Batching events
@@ -30,5 +30,19 @@ To capture multiple events at once, use `capture_batch()`:
 let event1 = posthog_rs::Event::new("event 1", "distinct_id_of_user_A");
 let event2 = posthog_rs::Event::new("event 2", "distinct_id_of_user_B");
 
-client.capture_batch(vec![event1, event2], false).await.unwrap();
+client.capture_batch(vec![event1, event2], false);
 ```
+
+### Flushing events
+
+`capture` and `capture_batch` return as soon as the event is queued. A background worker batches and sends events for you, so capturing never blocks on the network. Because delivery happens in the background, flush before your program exits or buffered events may be lost:
+
+```rust
+// Send queued events now (one delivery attempt per pending batch)
+client.flush().await;
+
+// Or flush, stop the background worker, and wait for it to finish (for example, on shutdown)
+client.shutdown().await;
+```
+
+With the blocking client (`default-features = false`), call `flush()` and `shutdown()` without `.await`.

contents/docs/product-analytics/_snippets/how-to-capture-anonymous-backend-and-api.mdx

@@ -64,7 +64,7 @@ let mut event = Event::new("your_event_name", "distinct_id_of_the_user");
 
 event.insert_prop("$process_person_profile", false).unwrap();
 
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 ```elixir

contents/docs/product-analytics/_snippets/how-to-capture-identified-events-backend.mdx

@@ -44,7 +44,7 @@ posthog.capture("distinct_id_of_the_user", "your_event_name", new HashMap<String
 ```rust
 let mut event = Event::new("your_event_name", "distinct_id_of_the_user");
 
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 ```elixir

contents/docs/product-analytics/identify.mdx

@@ -180,7 +180,7 @@ PostHog.capture("event_name", %{
 let mut event = Event::new("event_name", "distinct_id"); // the same distinct ID you use on the frontend
 // optional: set person properties
 event.insert_prop("$set", serde_json::json!({ "email": "max@hedgehogmail.com", "name": "Max Hedgehog" })).unwrap();
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 </MultiLanguage>
@@ -341,7 +341,7 @@ use posthog_rs::Event;
 let mut event = Event::new("$create_alias", "frontend_id");
 event.insert_prop("alias", "backend_id").unwrap();
 
-client.capture(event).await.unwrap();
+client.capture(event);
 ```
 
 ```bash