Rename Edge Config packages to Global Config

[luismeyer]

Summary

• replace direct @vercel/edge-config dependencies with @vercel/global-config
• rename @flags-sdk/edge-config to @flags-sdk/global-config
• update source imports, examples, documentation, lockfile, and release changeset

Verification

• adapter tests, type checks, and builds pass
• package and skill validation pass
• Biome checks pass
• docs and example TypeScript checks pass
• docs build compiles and passes TypeScript, then stops during page-data collection because FLAGS_SECRET is not set

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
flags-playground	Ready	Preview, Comment, Open in v0	Jul 29, 2026 3:18pm
flags-sdk-dev	Ready	Preview, Comment, Open in v0	Jul 29, 2026 3:18pm
flags-sdk-snippets	Ready	Preview, Comment, Open in v0	Jul 29, 2026 3:18pm
flags-sdk-sveltekit-snippets	Ready	Preview, Comment, Open in v0	Jul 29, 2026 3:18pm
shirt-shop	Ready	Preview, Comment, Open in v0	Jul 29, 2026 3:18pm
shirt-shop-api	Ready	Preview, Comment, Open in v0	Jul 29, 2026 3:18pm

[vercel]

Additional Suggestion:

Missing GLOBAL_CONFIG env var in examples/snippets/.env causes the custom adapter to throw at module load, failing the build during page-data collection for /.well-known/vercel/flags.

[luismeyer]

Addressed the review feedback in the latest commit:

• renamed EDGE_CONFIG to GLOBAL_CONFIG in examples/snippets/.env
• renamed the release workflow and Turbo environment entries
• verified pnpm --filter snippets build completes successfully, including page-data collection and static generation
• scanned all tracked files for edgeConfig, EdgeConfig, EDGE_CONFIG, and edge-config

Remaining matches are limited to historical changelogs, exact third-party API keys/classes, serialized connection-string fields, external URLs/endpoints, old-route redirect sources, and transitive dependency lockfile entries.

[luismeyer]

Updated remaining endpoints to Global Config:

• connection host: global-config.vercel.com
• REST API: /v1/global-config/{global_config_id}/items
• dashboard origin: /~/stores/global-config/...
• template URL: /templates/global-config
• updated examples and tests

Verification:

• @flags-sdk/global-config and LaunchDarkly tests/type checks pass
• snippets production build passes
• docs TypeScript check passes
• tracked endpoint scan has no https://edge-config, /v1/edge-config/, /~/stores/edge-config/, or templates/edge-config matches

Vercel documentation links still use /docs/storage/edge-config because the corresponding /docs/storage/global-config route currently returns 404.