fix: use standard GitHub API version in githubHeaders#5
Open
mmazur wants to merge 1 commit into
Open
Conversation
The githubHeaders function was sharing the Copilot API_VERSION constant
("2025-10-01"), which is only valid for Copilot endpoints. Standard
GitHub REST API endpoints (like /user) reject this version with HTTP 400.
Use the stable "2022-11-28" version for GitHub REST API calls instead.
Fixes QLHazyCoder#4
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
@QLHazyCoder 请您审核 |
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.
Summary
githubHeaders()was using the sharedAPI_VERSIONconstant ("2025-10-01"), which is only valid for Copilot API endpoints/user) reject this version with HTTP 400, causing "Failed to get user info" errors during the Admin UI device flow"2022-11-28"(a supported GitHub REST API version) ingithubHeaders()insteadFixes #4
Testing
Human here, this actually fixed my thing.