Rename Edge Config to Global Config across examples - #1538
Merged
Conversation
luismeyer
requested review from
a team,
dominiksipowicz,
goncy,
lfades,
lpalmes and
okbel
as code owners
July 23, 2026 10:22
Contributor
|
You must have Developer access to commit code to Vercel Examples on Vercel. If you contact an administrator and receive Developer access, commit again to see your changes. Learn more: https://vercel.com/docs/accounts/team-members-and-roles/access-roles#team-level-roles |
Contributor
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
luismeyer
marked this pull request as draft
July 24, 2026 09:33
luismeyer
force-pushed
the
luismeyer/fla-3104-phase-2-update-vercelexamples
branch
from
July 24, 2026 09:43
5044a3e to
1830ee7
Compare
AndyBitz
approved these changes
Jul 29, 2026
Swaps @vercel/edge-config for the renamed @vercel/global-config package and updates user-facing "Edge Config" mentions to "Global Config" in READMEs, comments, and UI copy. Env var names (EDGE_CONFIG), API endpoints, and third-party SDK option keys are left untouched since those haven't been renamed yet. Co-Authored-By: Luis Meyer <luis.meyer@vercel.com>
Speculatively targets @vercel/global-config@1.5.0 (unreleased), renames EDGE_CONFIG* env vars to GLOBAL_CONFIG*, and switches the apple-store REST call to the not-yet-public /v1/global-config endpoint. These examples won't build/deploy until the corresponding platform phases (env var rename, public API route, 1.5.0 release) ship. Note: feature-flag-launchdarkly now fails tsc/next build type checking because @launchdarkly/vercel-server-sdk still depends on the old @vercel/edge-config internally, so its init() rejects a @vercel/global-config client (DeepReadonly<T> structural mismatch). Left as-is per direction; needs a fix once LaunchDarkly's SDK updates its own dependency. Co-Authored-By: Luis Meyer <luis.meyer@vercel.com>
ecklf
approved these changes
Jul 29, 2026
…ase-2-update-vercelexamples # Conflicts: # flags-sdk/posthog/package.json # flags-sdk/posthog/pnpm-lock.yaml
lfades
approved these changes
Jul 29, 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
4 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
@vercel/edge-configfor the renamed@vercel/global-configpackage across all affectedpackage.jsonfiles and lockfiles.from '@vercel/edge-config'→from '@vercel/global-config').edge-middleware/*,flags-sdk/launchdarkly,internal/fields.json,rust/*/AGENTS.md, and the SvelteKit toolbar example.missing-edge-configpages/routes tomissing-global-config(apple-store, split, maintenance-page) and updates their internal redirects/component names.