Skip to content

Rename Edge Config packages to Global Config - #452

Merged
AndyBitz merged 11 commits into
mainfrom
rename-edge-config-to-global-config
Aug 4, 2026
Merged

Rename Edge Config packages to Global Config#452
AndyBitz merged 11 commits into
mainfrom
rename-edge-config-to-global-config

Conversation

@luismeyer

Copy link
Copy Markdown
Member

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

vercel Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated (UTC)
flags-playground Ready Ready Preview Aug 4, 2026 10:31am
flags-sdk-dev Ready Ready Preview Aug 4, 2026 10:31am
flags-sdk-snippets Ready Ready Preview Aug 4, 2026 10:31am
flags-sdk-sveltekit-snippets Ready Ready Preview Aug 4, 2026 10:31am
shirt-shop Ready Ready Preview Aug 4, 2026 10:31am
shirt-shop-api Ready Ready Preview Aug 4, 2026 10:31am

@vercel vercel Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix on Vercel

@luismeyer

Copy link
Copy Markdown
Member Author

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

Copy link
Copy Markdown
Member Author

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.

@socket-security

socket-security Bot commented Aug 4, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​@​vercel/​global-config@​1.5.07510010088100

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants