Repository navigation
fix: detect customer-portal API keys with -gov and -rl prefixes - #5852
Open
Sivadheeraj5356 wants to merge 3 commits into
Open
Sivadheeraj5356 wants to merge 3 commits into
Sivadheeraj5356 wants to merge 3 commits into
Conversation
Bugbot is paused — your team has an unpaid invoiceBugbot is paused because your team has an unpaid invoice. Pay it from the billing page in the Cursor dashboard and Bugbot resumes automatically. (requestId: b5071040-38c8-4e9a-9191-cbe83f2abd8c) |
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
This branch was previously deployed
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
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
Fixes #5850.
buildHeliconeApiKey generates customer-portal keys shaped [sp]k(-eu)?-cp(-gov)?(-rl)?- (and org keys [sp]k-helicone(-eu)?(-gov)?(-rl)?-), but the shared HELICONE_API_KEY_REGEX stopped at (-cp)?. Keys like sk-cp-rl-* and sk-cp-gov-* were therefore not recognized: containsHeliconeKey in the worker returned false for them, so buildProviderRequestHeaders did not strip them from outbound provider headers, and the identical regex copy in jawn's requestWrapper rejected them as malformed.
This extends the shared pattern with (-gov)?(-rl)? in the generator's segment order, in both copies.
Testing