chore(deps): update rust crate posthog-rs to v0.10.2#3482
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
d857875 to
d32db3e
Compare
d32db3e to
40e096b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.10.0→0.10.20.10.0→0.10.2Release Notes
posthog/posthog-rs (posthog-rs)
v0.10.2Compare Source
Patch changes
capture_batchwith an empty event list is now a no-op on both clients andboth capture paths — no HTTP request is sent (the v1 backend rejects empty
batches). Also derives
Debugfor the internal retryStepand pins that abody-less 2xx response is a terminal serialization error, not a retry. — Thanks @eli-r-ph!
v0.10.1Compare Source
Patch changes
4a6c67c Three fixes to the unstable
capture-v1pipeline (off by default):Error::Serialization.posthog-rs/<version>(previouslyposthog-rust/<version>) in theposthog-sdk-infoanduser-agentheaders. The name segment now matches the$libvalue the v0 path sends, so capture-side$lib/$lib_versionmaterialization attributes V1 traffic correctly in SDK Health, usage reports, and Library columns.$feature_flag_calledevents through the V1 analytics endpoint whencapture-v1is 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)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.