Repository navigation
[PRO-4275] Enforce docs analytics consent with Fern 5.169.0 - #1405
Draft
haotian-vapi wants to merge 1 commit into
Draft
haotian-vapi wants to merge 1 commit into
haotian-vapi wants to merge 1 commit into
Conversation
[Client consent enforcement](https://linear.app/vapi/issue/PRO-4275/client-consent-enforcement) ## Description Pin Fern 5.169.0 with the approved package hash and update both compatibility wrapper markers. Integrate native consent before analytics initialization, latch withdrawal until reload, remove ungated GA4/unverified custom collectors, and add current consent headers to first-party fetch/XHR requests. | Before (audit) | After (generated-runtime evidence) | | --- | --- | | Native/custom analytics can initialize without resolved permission | Denial blocks optional analytics; grant permits collection; withdrawal stops further sends | | Native runtime lacks the approved consent integration | Pinned package hash and both wrapper compatibility checks pass | ## Testing Steps - [x] Generate and exercise the local docs runtime: six Chromium scenarios passed, including CI preview startup. - [x] Run 13 privacy/header, 39 subscription, 14 cache and 18 CLI compatibility checks. - [x] Run Fern check: zero errors, 19 existing warnings. - [ ] Verify hosted provider/region configuration, full API-reference playground and search backend. The historical 37-probe CLI suite was unavailable; 18 available compatibility probes were run. Analytics regrant after withdrawal requires reload. The [Evidence Report](https://linear.app/vapi/document/pro-4275-evidence-report-95d2b5d18e2a) includes tested revisions, simplify-cycle results and the initial newsletter-interception incident.
Contributor
|
🌿 Preview your docs: https://vapi-preview-01a1bea8-c885-736d-be60-67f1d80e918e.docs.buildwithfern.com |
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.
Client consent enforcement
Description
Pin Fern 5.169.0 with the approved package hash and update both compatibility wrapper markers. Integrate native consent before analytics initialization, latch withdrawal until reload, remove ungated GA4/unverified custom collectors, and add current consent headers to first-party fetch/XHR requests.
Testing Steps
The historical 37-probe CLI suite was unavailable; 18 available compatibility probes were run. Analytics regrant after withdrawal requires reload. The Validation Report includes tested revisions, simplify-cycle results and the initial newsletter-interception incident.