flags

Fix the dependency versions reported by all 21 open Dependabot alerts (#1188–#1208). Update Vite from 8.1.5 to 8.1.6 in all 17 direct dependency declarations. Require follow-redirects 1.16.1 or later and launch-editor 2.14.2 or later through workspace overrides. Update the lockfile. All other package versions remain unchanged. Validation: 1,340 tests passed, with one skipped. Type checks, Biome, dependency consistency checks, package validation, and package, docs, and Svelte builds passed. The docs build used a temporary local test secret. Browser tests were not run. All 21 alerts were checked against the final manifests and lockfile. Automatic approval review blocked because it sends dependency metadata to npm; the GitHub alerts were used for verification.

Why Lets the dashboard's flag evaluations graph break down evaluations by the served config revision. \ events now carry an optional \ (\, omitted when undefined, same as \). \ is part of the evaluation aggregation key, so evaluations of different revisions are not merged. Read-failure paths have no datafile and omit it. First of a cross-repo change: infra fact schema, api ingestion + storage, then the dashboard follow. Validation In : passes (biome) passes passes (1064 tests); new tests cover revision in payload (incl. ), omission when undefined, distinct revisions not merged (unit and stream black-box), and no revision on the read-failure path 🤖 Generated with Claude Code

Splits into two skills. Agents pick a skill by its description, and one description cannot cover both "roll this out to 10%" and "wire with precompute". #554 pushed the SDK skill toward planning, which also pulled Vercel-specific guidance into a provider-neutral skill. What New : stack-agnostic entry point. Planning, choosing an integration (Flags SDK / / OpenFeature), the CLI, credentials, lifecycle and safety checks. Hands Next.js and SvelteKit code to . : implementation only. CLI management, "Choose an approach", and the Express example move out; pointers to stay so it works standalone. Docs: framework pages and homepage keep installing ; the Vercel provider page installs both with explicit flags (no opens an interactive picker now that the repo has two skills). "Add a flag to my Next.js app" matches both descriptions on purpose; routes straight to when is already in . Follow-ups: re-vendor into vercel-plugin and Vercel Agent, add a hand-off, update vercel.com docs (vercel/front#90990). Validation**: passes, all relative links and docs URLs resolve, the snippet matches .