Skip to content

fix: send pipeboard-cli User-Agent on all HTTP requests - #14

Merged
nictuku merged 1 commit into
mainfrom
nictuku/custom-user-agent
Apr 5, 2026
Merged

nictuku merged 1 commit into
mainfrom
nictuku/custom-user-agent

Conversation

@nictuku

@nictuku nictuku commented Apr 5, 2026

Copy link
Copy Markdown
Contributor

Summary

  • RESTClient and FetchToolsHash were defaulting to Go's Go-http-client/1.1 User-Agent because they never set the header.
  • Now all HTTP paths (MCP client, REST client, and tools-hash fetch) consistently send pipeboard-cli/<version>.

Test plan

  • Run make build && make test
  • Verify server logs show pipeboard-cli/... instead of Go-http-client/1.1

RESTClient and FetchToolsHash were using Go default User-Agent
(Go-http-client/1.1). Now all HTTP paths consistently send
pipeboard-cli/<version>.
@nictuku
nictuku merged commit 94fcd91 into main Apr 5, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant