feat!: use capture v1 by default - #209
Draft
marandaneto wants to merge 1 commit into
Draft
Conversation
marandaneto
commented
Aug 10, 2026
Comment on lines
+14
to
+25
| ## Capture pipeline | ||
|
|
||
| The V1 capture pipeline is enabled by default. To continue using the legacy V0 | ||
| pipeline, disable the default features and explicitly enable the other features | ||
| your application needs: | ||
|
|
||
| ```toml | ||
| posthog-rs = { version = "1", default-features = false, features = ["async-client", "error-tracking"] } | ||
| ``` | ||
|
|
||
| This example retains the default asynchronous client and error tracking while | ||
| opting out of `capture-v1`. |
Member
Author
There was a problem hiding this comment.
TBD: if we remove the capture-v0 and v1 altogether and strip all capture v0 code as well
Member
Author
|
do not merge because its a breaking change, i want to stack a few changes together before releasing v1 |
Contributor
posthog-rs-v1 Compliance ReportDate: 2026-08-10 19:03:28 UTC ✅ All Tests Passed!111/111 tests passed Capture_V1 Tests✅ 94/94 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
Contributor
posthog-rs-v0 Compliance ReportDate: 2026-08-10 19:03:33 UTC ✅ All Tests Passed!46/46 tests passed Capture Tests✅ 29/29 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
|
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.
💡 Motivation and Context
The V1 capture pipeline is ready to become the supported default as part of #207. Existing applications should still be able to remain on V0 while they prepare to migrate.
This adds
capture-v1to the default Cargo features and documents how to opt out by disabling default features. The CI matrix now tests the V1 default and an asynchronous V0 fallback. The compliance adapters disable dependency defaults so the V0 and V1 suites continue to build the intended pipeline.💚 How did you test it?
cargo fmt -- --checkcargo build --verbosecargo build --verbose --no-default-features --features async-client,error-trackingcargo testcargo test --workspacecargo test --no-default-features --features async-client,error-trackingcargo test --no-default-features --features capture-v1cargo test --no-default-features --features error-trackingcargo test --no-default-features --features error-tracking,capture-v1cargo test --verbose --features e2e-test --no-default-featurescargo clippy -- -D warningscargo clippy --no-default-features --features async-client,error-tracking -- -D warningsscripts/check-public-api.shcargo publish --dry-run --lockedcapture-v1.📝 Checklist
If releasing new changes
sampo addto generate a changeset file