build(deps): bump the major group across 1 directory with 3 updates

[dependabot]

Bumps the major group with 3 updates in the / directory: posthog-rs, sysinfo and rmcp.

Updates posthog-rs from 0.15.1 to 0.17.0

Release notes

Sourced from posthog-rs's releases.

0.17.0

Minor changes

• f00e91b General on_error observability hook. Register one or more hooks with ClientOptionsBuilder::on_error to observe terminal failures across every SDK network surface without giving up the non-blocking API: a capture batch the SDK gave up delivering (permanent reject, exhausted retries, serialization failure, or — on the capture-v1 pipeline — a 2xx whose per-event verdicts left events unpersisted), a failed remote /flags request, and a failed local-evaluation definitions poll. Hooks fire in registration order and may be invoked from whichever thread reaches the failure (the background transport worker, a flags request, or the poller).

  Each hook receives a &PostHogError<'_>, a #[non_exhaustive] enum with one variant per surface (Capture, FeatureFlags, LocalEvaluation), each carrying an enriched, #[non_exhaustive] failure struct read through accessors: CaptureFailure (cause, HTTP status, attempt, lost-event count, historical-migration flag, and — under capture-v1 — request id, per-event event_results, and the parsed V1ErrorResponse), FlagsFailure (cause, endpoint, distinct id, status, body), and LocalEvaluationFailure (cause, status; the personal API key is never surfaced). The failure is passed by reference and borrows from the caller, so the common (hookless) path stays allocation-free. New public exports: PostHogError, CaptureFailure, FlagsFailure, LocalEvaluationFailure, and (under capture-v1) V1ErrorResponse.

  The hook is observability-only and MUST NOT call back into the SDK (no capture/capture_batch/capture_exception, flush, or shutdown): emitting an event while handling a capture failure forms an amplification loop. The hook is Fn + Send + Sync and invoked without holding any SDK lock, so it may run concurrently on multiple threads and must be internally thread-safe. Hook panics are caught and ignored. Registering at least one hook silences the default WARN logged for terminal capture batch rejects/exhaustion, since the caller now owns that signal; other drop warnings and the existing /flags and poller logs are unaffected.

  Also makes the blocking local-evaluation poller's background thread shut down promptly: it now wakes to check the stop signal in short steps instead of sleeping the full poll interval, so stop/Drop no longer blocks for up to a whole interval (previously up to the configured poll_interval_seconds). — Thanks @​eli-r-ph!

0.16.0

Minor changes

• c2766cd Native symbolication for error tracking: captured exceptions and panics now attach each frame's instruction_addr and an event-level $debug_images list, so PostHog can symbolicate native (Rust/C/C++) stack frames server-side against symbols uploaded with posthog-cli. Debug ids match the server/CLI convention (GNU build id on ELF, LC_UUID on Mach-O, GUID+age on Windows PDB). Behind the default-on error-tracking feature. — Thanks @​cat-ph!

Changelog

Sourced from posthog-rs's changelog.

0.17.0 — 2026-07-02

Minor changes

• f00e91b General on_error observability hook. Register one or more hooks with ClientOptionsBuilder::on_error to observe terminal failures across every SDK network surface without giving up the non-blocking API: a capture batch the SDK gave up delivering (permanent reject, exhausted retries, serialization failure, or — on the capture-v1 pipeline — a 2xx whose per-event verdicts left events unpersisted), a failed remote /flags request, and a failed local-evaluation definitions poll. Hooks fire in registration order and may be invoked from whichever thread reaches the failure (the background transport worker, a flags request, or the poller).

  Each hook receives a &PostHogError<'_>, a #[non_exhaustive] enum with one variant per surface (Capture, FeatureFlags, LocalEvaluation), each carrying an enriched, #[non_exhaustive] failure struct read through accessors: CaptureFailure (cause, HTTP status, attempt, lost-event count, historical-migration flag, and — under capture-v1 — request id, per-event event_results, and the parsed V1ErrorResponse), FlagsFailure (cause, endpoint, distinct id, status, body), and LocalEvaluationFailure (cause, status; the personal API key is never surfaced). The failure is passed by reference and borrows from the caller, so the common (hookless) path stays allocation-free. New public exports: PostHogError, CaptureFailure, FlagsFailure, LocalEvaluationFailure, and (under capture-v1) V1ErrorResponse.

  The hook is observability-only and MUST NOT call back into the SDK (no capture/capture_batch/capture_exception, flush, or shutdown): emitting an event while handling a capture failure forms an amplification loop. The hook is Fn + Send + Sync and invoked without holding any SDK lock, so it may run concurrently on multiple threads and must be internally thread-safe. Hook panics are caught and ignored. Registering at least one hook silences the default WARN logged for terminal capture batch rejects/exhaustion, since the caller now owns that signal; other drop warnings and the existing /flags and poller logs are unaffected.

  Also makes the blocking local-evaluation poller's background thread shut down promptly: it now wakes to check the stop signal in short steps instead of sleeping the full poll interval, so stop/Drop no longer blocks for up to a whole interval (previously up to the configured poll_interval_seconds). — Thanks @​eli-r-ph!

0.16.0 — 2026-07-01

Minor changes

• c2766cd Native symbolication for error tracking: captured exceptions and panics now attach each frame's instruction_addr and an event-level $debug_images list, so PostHog can symbolicate native (Rust/C/C++) stack frames server-side against symbols uploaded with posthog-cli. Debug ids match the server/CLI convention (GNU build id on ELF, LC_UUID on Mach-O, GUID+age on Windows PDB). Behind the default-on error-tracking feature. — Thanks @​cat-ph!

Commits

• d99286b chore: Release v0.17.0 [skip ci]
• f00e91b feat: general on_error observability hook (#167)
• 2b76e52 chore: Release v0.16.0 [skip ci]
• c2766cd feat: capture native instruction addresses and debug images (#158)
• 960aa57 Exclude eyre from default in-app frames & add eyre example (#168)
• 2d0d769 ci: update SDK harness to 0.9.0 (#166)
• See full diff in compare view

Updates sysinfo from 0.38.4 to 0.39.5

Changelog

Sourced from sysinfo's changelog.

0.39.5

• macOS: Fix build for apple app store

0.39.4

• Unix: Fix soundness issue when retrieving user's groups.
• macOS: Add new macOS version name.
• macOS: Fix inaccurate open_files returned value.

0.39.3

• Unix: Fix retrieval of Network::mac_addr.
• Linux: Improve retrieval of process information if process terminates while doing so.

0.39.2

• Windows: Greatly improve performance of System::refresh_cpu_specifics when CPU usage is not requested.
• iOS: Fix compilation error when user feature is enabled.
• Linux: Correctly set thread information for processes.

0.39.1

• Linux: Fix wrong network numbers computation.

0.39.0

• Update minimum supported rust version to 1.95.
• Add new NetworkData::operational_state API.
• Add new Process::cgroup_limits API (only returning data on Linux).
• All supported systems other than Windows: Improve performance of Networks::refresh*.
• All supported systems other than Windows: Fix soundness issue when retrieving users.
• Linux: Take into account parent cgroup memory limits.
• Linux: Fix panic when retrieving process information on ESXi.
• FreeBSD: Use the name of dataset as name for zfs disks.

Commits

• 029025e Update crate version to 0.39.5
• 78205e7 Update CHANGELOG for 0.39.5
• 2a39746 Fix build for apple app store
• c07bb44 Update CHANGELOG for 0.39.4
• 559b07d Update crate version to 0.39.4
• 07e3177 Linux: Fix soundness issue when retrieving user groups
• 79943ec Add new macOS version name
• 86af156 Added failure handling for open_files()
• 634e1cf fix: inaccurate open_files() implementation (#1681) (#1682)
• 3d1c52a Update crate version to 0.39.3
• Additional commits viewable in compare view

Updates rmcp from 1.8.0 to 2.0.0

Release notes

Sourced from rmcp's releases.

rmcp-macros-v2.0.0

Added

• [breaking] align model types with MCP 2025-11-25 spec (#927)

Fixed

• fill missing fully qualified syntax in prompt_handler macros (#866)

Other

• align README examples with v2 model API (#928)

rmcp-v2.0.0

Migration guide: modelcontextprotocol/rust-sdk#926

Added

• [breaking] (rmcp) add Audio variant to PromptMessageContent (#865)
• [breaking] align model types with MCP 2025-11-25 spec (#927)
• deprecate roots/sampling/logging types (#923)

Fixed

• prevent OAuth resource spoofing (#937)
• block oauth metadata ssrf (#935)
• prevent streamable HTTP session leak (#934)
• fill missing fully qualified syntax in prompt_handler macros (#866)

Other

• consolidate repeated rmcp tests (#931)
• align README examples with v2 model API (#928)

Commits

• 67a3085 chore: release v2.0.0 (#920)
• c1a8b29 fix: prevent OAuth resource spoofing (#937)
• eb435c6 fix: block oauth metadata ssrf (#935)
• dfa7fd6 fix: prevent streamable HTTP session leak (#934)
• e1af378 chore: consolidate repeated rmcp tests (#931)
• 4b9bea7 Revert "feat!: relax tool result structuredContent type (#919)" (#932)
• b8a936c feat!: relax tool result structuredContent type (#919)
• 4158528 fix: fill missing fully qualified syntax in prompt_handler macros (#866)
• d1cabb4 feat: deprecate roots/sampling/logging types (#923)
• f07ee4a docs: align README examples with v2 model API (#928)
• Additional commits viewable in compare view

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.