Repository navigation
Conversation
Co-Authored-By: Claude Code <noreply@anthropic.com>
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
luismeyer
marked this pull request as ready for review
November 11, 2026 08:17
This branch was successfully 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.
Why
origin: { provider: 'vercel' }, with noprojectId. OnlycreateClient({ projectId })for a connected project set one.getProviderDatafromflags/nextandflags/sveltekitpasses the origin through unchanged, so a discovery endpoint built with it could not say which project a Vercel Flags flag belongs to.getProviderDatafrom@flags-sdk/vercelwas unaffected because it resolves the project itself.projectIdto attribute a deployment's code references to the project, for example to mark a flag as seen in production. Without it the flag is never marked.What
VERCEL_PROJECT_IDis set. Clients with an SDK key are unchanged.getProviderDatafrom@flags-sdk/vercelnow skips its datafile lookup for these origins, since the origin already names the project.Validation
getProviderDatafromflags/next: the flag was stored withorigin: { provider: 'vercel' }.VERCEL_PROJECT_ID, so their origin stays as before. vercel/api handles that case on its side (companion PR).🤖 Generated with Claude Code