chore(release): version package - #36
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 5, 2026 09:21
50eb8a5 to
a0b4a83
Compare
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 15, 2026 08:24
a0b4a83 to
72847b7
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 was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
trakoo@1.1.0
Minor Changes
Report the full page URL from the browser adapter so campaign parameters survive.
BrowserAnalyticsbuilt its page context fromwindow.location.pathnamealone, so the query string never left the browser and everyutm_source/utm_medium/utm_campaignvalue was dropped before delivery — campaign traffic arrived in the dashboard as direct. The adapter now also populates theurl,search,hostandprotocolfields thatEventContext["page"]already declared, from a singlegetPageContext()snapshot shared byinitialize()andpageView(). (#37)updateContext()also merges the page snapshot instead of rebuilding it frompath,titleandreferrer, which had silently discarded every other declared field. Without that, only the immediatepageView()call carried a URL —track()andpageLeave()read the stored context and still saw none. Partial page updates now merge rather than erase, and an emptysearchis kept as a real value so a URL with no query string cannot inherit the previous page's parameters.This reaches any provider that reports a URL. OpenPanel, Bento, EmitKit, Pirsch and the proxy all read
context.page.urland fall back tocontext.page.path; until now that fallback was always taken. OpenPanel'sscreenView()consequently receives the full URL, which is what its own SDK sends when it tracks screen views itself, so its__pathchanges from a bare pathname to an absolute URL and its dashboard resolves the path and domain server-side. OpenPanel'sscreenView()also dedupes on the value it is handed, so two visits to one pathname under different query strings are now distinct: an app that callspageView()when query parameters change — filters, pagination, tabs — emits onescreen_viewper change where it previously emitted one in total. Expect page-view counts on those routes to rise.Nothing new is collected — the query string was always present in the browser — but a site that puts sensitive values in query parameters now sends them to its analytics provider, so exclude those before they reach the URL.
Report OpenPanel delivery failures instead of dropping them. OpenPanel's SDKs answer an HTTP 401 by returning
nullwithout throwing, retrying or logging, so a wrong client ID, a rotated secret or a browser origin the project does not allow stopped analytics silently. Both OpenPanel providers now acceptonDeliveryFailureand log rejections when no handler is configured. The failure reports the reason, status, attempt count, envelope type and ingestion URL, never event properties, and delivery still resolves so a rejected event never becomes an application error. (#34)