feat(next): enable same-origin tracing headers by default#3941
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Reviews (1): Last reviewed commit: "chore(next): update tracing headers chan..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Contributor
Contributor
|
Size Change: +609 B (0%) Total Size: 16.9 MB
ℹ️ View Unchanged
|
turnipdabeets
approved these changes
Jun 23, 2026
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
2 participants
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.
Problem
@posthog/nextalready reads PostHog tracing headers on the server and prioritizes them over cookie identity, but the client provider did not enable same-origin tracing headers by default. That meant server-sidegetPostHog()/getServerSidePostHog()could only use those headers when users explicitly configured them.Changes
@posthog/nextclient initialization to add tracing headers for the current same-origin hostname.@posthog/next.Release info Sub-libraries affected
Libraries affected
Checklist
If releasing new changes
pnpm changesetto generate a changeset file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Implemented with Pi coding agent assistance. The main decision was to keep the runtime hostname lookup in the client provider, since it depends on
window.location.hostname, while preserving all explicit user tracing-header configuration and opt-outs.Smoke tested with: