Repository navigation
feat: prepare browser telemetry through an approved proxy - #26
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Add browser telemetry to the shared layout, enabled only when an approved HTTPS proxy is configured at build time. Collector credentials stay out of browser code.
Tested: Astro check, lint, all 40 tests and production build pass locally. Native Chromium confirms no cookies or Referer header. Build/vitals/privacy regressions failed before their fixes; buffered LCP/CLS mutations fail.
Not checked: live browser delivery, Loki or probe verification. No endpoint is configured or deployed; maintainers must agree collection before rollout.