feat(client): default User-Agent header for SDK attribution (DAK-7617) - #214
Merged
Conversation
Set `User-Agent: dakera-js/<version>` on the default request headers so the Dakera engine's server-side telemetry (DAK-7617) can attribute JS/TS SDK usage. Placed before `...options.headers` so callers can still override. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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
1 participant
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.
Sets
User-Agent: dakera-js/0.11.104on the client's default request headers so the Dakera engine's server-side telemetry (DAK-7617) can attribute JS/TS SDK usage.Change
SDK_VERSIONconstant insrc/client.ts(kept in sync withpackage.json).'User-Agent': \dakera-js/${SDK_VERSION}`to the default headers in the constructor, placed **before**...options.headers` so a caller can still override it.Caveat
User-Agentis a forbidden fetch header in browsers and will be silently dropped there — it is honored in Node. This is acceptable for telemetry attribution (server-side clients are the primary signal), and is noted with an inline code comment.🤖 Generated with Claude Code