fix: when Bolt run on wrangler there are not default User-Agent headers when request to Github are made #1981
Conversation
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
…when request to Github are made.
gafitescu
changed the title
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.
Local Development (pnpm run dev)
Node.js runtime: Automatically adds a default User-Agent header like node-fetch/X.X.X or similar
Automatic headers: Node.js HTTP libraries include standard headers that GitHub API accepts
Permissive: GitHub API is more lenient with requests from development environments
Cloudflare Workers (Wrangler)
V8 runtime: Uses the Web API fetch() which doesn't automatically add User-Agent headers
Stricter validation: GitHub API enforces User-Agent header requirements more strictly for production-like environments
Security: Cloudflare Workers strip or modify certain headers for security reasons