chore: Release v0.10.1 [skip ci]

Author: releaser-posthog-rs[bot]

.sampo/changesets/capture-v1-2xx-sdk-info-flag-events.md

@@ -1,5 +1,15 @@
 # posthog-rs
 
+## 0.10.1 — 2026-06-10
+
+### Patch changes
+
+- [4a6c67c](https://github.com/posthog/posthog-rs/commit/4a6c67c3d937f185993f256ddda2c087f5020980) Three fixes to the unstable `capture-v1` pipeline (off by default):
+  
+  - Accept any 2xx HTTP status as success on V1 capture responses instead of exactly 200, so a future 201/202/207 from capture is not misclassified as a connection error. Malformed bodies on 2xx still surface as `Error::Serialization`.
+  - Send the canonical SDK identity `posthog-rs/<version>` (previously `posthog-rust/<version>`) in the `posthog-sdk-info` and `user-agent` headers. The name segment now matches the `$lib` value the v0 path sends, so capture-side `$lib`/`$lib_version` materialization attributes V1 traffic correctly in SDK Health, usage reports, and Library columns.
+  - Route `$feature_flag_called` events through the V1 analytics endpoint when `capture-v1` is enabled (previously they always took the legacy v0 path, splitting the pipeline). Shipping stays fire-and-forget with a single attempt and no retry loop, matching the v0 flag-event semantics on both the async and blocking clients. — Thanks @eli-r-ph!
+
 ## 0.10.0 — 2026-06-05
 
 ### Minor changes

CHANGELOG.md

@@ -1,7 +1,7 @@
 [package]
 name = "posthog-rs"
 license = "MIT"
-version = "0.10.0"
+version = "0.10.1"
 authors = ["PostHog <engineering@posthog.com>"]
 description = "The official Rust client for Posthog (https://posthog.com/)."
 repository = "https://github.com/posthog/posthog-rs"