Skip to content

chore(deps): update rust crate posthog-rs to v0.10.2#3482

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/posthog-rs-0.x-lockfile
Open

chore(deps): update rust crate posthog-rs to v0.10.2#3482
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/posthog-rs-0.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
posthog-rs dependencies patch 0.10.00.10.2
posthog-rs workspace.dependencies patch 0.10.00.10.2

Release Notes

posthog/posthog-rs (posthog-rs)

v0.10.2

Compare Source

Patch changes
  • 7131402 capture_batch with an empty event list is now a no-op on both clients and
    both capture paths — no HTTP request is sent (the v1 backend rejects empty
    batches). Also derives Debug for the internal retry Step and pins that a
    body-less 2xx response is a terminal serialization error, not a retry. — Thanks @​eli-r-ph!

v0.10.1

Compare Source

Patch changes
  • 4a6c67c 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!

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot enabled auto-merge (squash) June 10, 2026 21:06
@github-actions github-actions Bot added the type: chore Routine tasks like conversions, reorganization, and maintenance work. label Jun 10, 2026
@renovate renovate Bot force-pushed the renovate/posthog-rs-0.x-lockfile branch from d857875 to d32db3e Compare June 11, 2026 02:17
@renovate renovate Bot force-pushed the renovate/posthog-rs-0.x-lockfile branch from d32db3e to 40e096b Compare June 11, 2026 05:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: chore Routine tasks like conversions, reorganization, and maintenance work.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants