-
Notifications
You must be signed in to change notification settings - Fork 2
Upstream release: ctx7@0.5.7 #21
Copy link
Copy link
Open
Labels
automatedCreated by automated workflowCreated by automated workflowupstream-releaseNew upstream Context7 release detectedNew upstream Context7 release detected
Description
Activity
Metadata
Metadata
Assignees
Labels
automatedCreated by automated workflowCreated by automated workflowupstream-releaseNew upstream Context7 release detectedNew upstream Context7 release detected
New Upstream Release Detected
Tag:
ctx7@0.5.7Previous:
@upstash/context7-mcp@3.2.5Release: https://github.com/upstash/context7/releases/tag/ctx7%400.5.7
Release Notes
Patch Changes
ctx7 setupnow writes the API key as a standardAuthorization: Bearer <key>header instead of a customCONTEXT7_API_KEYheader. Codex resolves a server's auth mode frombearer_token_env_varor a header literally namedAuthorization, so a custom name read as "no credential configured": Codex fell through to an OAuth credential stored against the same server name and URL, refreshed it during startup, and when that refresh token was dead the server failed withinvalid_grantbefore the API key was ever sent. The hosted endpoint accepts both header forms, so existing configs keep working.Action Required
Review the upstream changes and determine if this fork needs updates:
This issue was created automatically by the release monitor workflow.