fix: name the key a bare secret/publishable mode rejected - #155
Merged
Merged
Conversation
commit: |
kallebysantos
approved these changes
Sep 11, 2026
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.
When a
secretorpublishablemode rejects anapikeythat is a valid key of the same kind held under another name, theINVALID_API_KEYhint now names that key and points at thesecret:<name>orsecret:*mode that would accept it, anddetails.matchedKeyNamecarries the name. Bare modes match only the key nameddefault, so a named key sent to baresecretused to report "matched no configured key", which sent callers hunting for a mismatch that did not exist. Key values never appear in the hint or details, and a key that matches nothing keeps the existing hint. The auth-modes docs also gain a note that the Vercel integration syncs the most recently created secret key, so functions called from Vercel-hosted code should usesecret:*or a dedicated named key.