Flags SDK Updates & Release Notes

Follow

93 updates curated from 1 source by the Releasebot Team. Last updated: Nov 20, 2026

Get this feed:
  • Nov 20, 2026
    • Date parsed from source:
      Nov 20, 2026
    • First seen by Releasebot:
      Nov 20, 2026
    Vercel logo

    Flags SDK by Vercel

    Flags SDK adds Vercel KMS support so flag values, overrides, access proofs, and precomputed codes can work without FLAGS_SECRET on Vercel, while retaining secret-based behavior and providing safer fallbacks when keys or project details are unavailable.

    Minor Changes #586 3cc264b Thanks @luismeyer! - encryptFlagValues encrypts with the public key of Vercel when there is no FLAGS_SECRET, instead of throwing. In SvelteKit, createHandle and encryptFlagValues work without FLAGS_SECRET too: the flag values of a page are encrypted with the public key. This fallback is silent. Before, a secret which is undefined or empty (e.g. encryptFlagValues(values, process.env.TYPO)) threw an error. Now the values are encrypted with the public key, and decryptFlagValues can not read them, because only Vercel can decrypt them: it logs a warning and returns undefined. decryptFlagValues, encryptFlagDefinitions and decryptFlagDefinitions keep working only with a FLAGS_SECRET. The project of the host is also read from the OIDC token of the request (x-vercel-oidc-token), so a deployment which does not expose the system environment variables works too. #589 e248a06 Thanks @luismeyer! - verifyAccess accepts short-lived tokens which Vercel signs with Vercel KMS, so the Flags Discovery Endpoint (/.well-known/vercel/flags) works on Vercel without a FLAGS_SECRET. These tokens are signed by a separate Vercel KMS issuer, not the issuer of signed overrides. Proofs encrypted with the FLAGS_SECRET keep working exactly as before. Without a secret, verifyAccess now returns false for such a proof instead of throwing. When there is no secret and the host can not verify signed tokens (a self-hosted app, local development without vercel env pull, or a project which does not expose the system environment variables), verifyAccess logs a warning which names the fix. #587 3b5d8ec Thanks @luismeyer! - Accept flag overrides which the Vercel Toolbar signs with Vercel KMS, so overrides work on Vercel without a FLAGS_SECRET. On Vercel, or locally after vercel env pull, the SDK verifies signed override tokens with the public keys of Vercel, which it keeps in memory. decryptOverrides accepts them too, for apps which read the cookie themselves. Tokens encrypted with the FLAGS_SECRET keep working exactly as before. The cookie is still vercel-flag-overrides. The host must know that it runs for a Vercel project. On Vercel, it reads the project from the system environment variables (VERCEL, VERCEL_PROJECT_ID), or from the OIDC token of the request (x-vercel-oidc-token). With that token, a deployment also checks the team of a signed token. Locally, vercel env pull supplies the VERCEL_OIDC_TOKEN. SvelteKit also reads it from $env during vite dev. A signed token which the host can not use is ignored, with a warning which names the cause: the host can not verify signed tokens, the public keys do not load, or the token is for a different project or environment. Without a FLAGS_SECRET, a Next.js flag now ignores an overrides cookie which the host can not read (e.g. an encrypted cookie from before the secret was removed). Before, it threw flags: Missing FLAGS_SECRET. Add signOverrides, which asks Vercel to sign flag overrides for the project and the environment of the host, e.g. for end-to-end tests of a project without a FLAGS_SECRET. It uses the OIDC token of the host: of the request on a deployment, or the VERCEL_OIDC_TOKEN of vercel env pull. #597 0d8720f Thanks @luismeyer! - Precompute works on Vercel without a FLAGS_SECRET. When there is no secret, precompute, serialize, deserialize, getPrecomputed and generatePermutations (Next.js and SvelteKit) sign the code with a key derived from VERCEL_DEPLOYMENT_KEY, which Vercel sets for the build and for the runtime of a deployment. Each deployment has its own key, so a code is only valid inside the deployment which created it. Set FLAGS_SECRET or FLAGS_PRECOMPUTE_SECRET, or pass a secret, if a code must be valid in another deployment or project. The new variable FLAGS_PRECOMPUTE_SECRET sets a secret for precompute only. It is only used when there is no FLAGS_SECRET. The order is: a secret passed to the function, FLAGS_SECRET, FLAGS_PRECOMPUTE_SECRET, the key of the deployment, the public secret outside of Vercel. In SvelteKit, pass the same secret to createHandle, precompute and generatePermutations, or none to all of them. In the local development of a Vercel project (e.g. next dev or a local next build && next start after vercel env pull, which writes a VERCEL_OIDC_TOKEN for the environment development), these functions use a fixed, public secret when there is no other one. Anyone can create a code with it, so they warn one time when NODE_ENV is not development. Without such a token, e.g. on a custom host, they throw without a secret, as before. In a Turborepo task, a cache hit replays codes of another deployment, because VERCEL_DEPLOYMENT_KEY is not part of the hash of the task. Add VERCEL_DEPLOYMENT_KEY to the env of the task in turbo.json, or set FLAGS_PRECOMPUTE_SECRET. On Vercel without a secret and without VERCEL_DEPLOYMENT_KEY (a project which does not expose the system environment variables, or a build with vercel build which is deployed with vercel deploy --prebuilt), these functions throw as before. Patch Changes #586 3cc264b Thanks @luismeyer! - Without a FLAGS_SECRET, encryptFlagValues no longer throws when the public key of Vercel does not load (e.g. the key host is down, or a request times out). It logs a warning, at most one time in 30 seconds, and returns an empty string, so the build or the render does not fail. The flag values are only for the Vercel Toolbar: the page has none until it renders again. FlagValues of flags/react renders nothing for an empty string. If you render the script tag with data-flag-values yourself, leave it out when the value is empty. In SvelteKit, createHandle already rendered the page without the flag values; encryptFlagValues of flags/sveltekit now returns an empty string too. encryptFlagValues still throws when there is neither a secret nor a project ID, when the project ID is too long, and when the secret is not valid. With a secret nothing changes.

    Original source
  • Nov 19, 2026
    • Date parsed from source:
      Nov 19, 2026
    • First seen by Releasebot:
      Nov 19, 2026
    • Modified by Releasebot:
      Nov 21, 2026
    Vercel logo

    Flags SDK by Vercel

    Flags SDK adds a snapshotsDir option to write each datafile as <key>.json for build tools to embed in functions.

    Minor Changes

    #605 5f15ef3 Thanks @AndyBitz! - Add a snapshotsDir option that also writes each datafile as <key>.json for build tools to embed into functions

    Original source
  • All of your release notes in one feed

    Join Releasebot and get updates from Vercel and hundreds of other software products.

    Create account
  • Nov 19, 2026
    • Date parsed from source:
      Nov 19, 2026
    • First seen by Releasebot:
      Nov 19, 2026
    • Modified by Releasebot:
      Nov 21, 2026
    Vercel logo

    Flags SDK by Vercel

    Flags SDK now includes Vercel project IDs in OIDC origin data, helping discovery endpoints identify which project a flag belongs to.

    Patch Changes

    #595 072184f Thanks @luismeyer! - The client's origin now includes the projectId of the deployment's own project when it authenticates with OIDC and VERCEL_PROJECT_ID is set. Flags discovery endpoints that pass the origin through, such as getProviderData from flags/next, now report which project a Vercel Flags flag belongs to.

    Original source
  • Nov 19, 2026
    • Date parsed from source:
      Nov 19, 2026
    • First seen by Releasebot:
      Nov 19, 2026
    Vercel logo

    Flags SDK by Vercel

    @flags-sdk/[email protected]

    Flags SDK now supports OIDC-based project data in local development before Vercel Flags is activated.

    Patch Changes #602 75fa303 Thanks @luismeyer! - getProviderData works before Vercel Flags is activated for a project in local development. When the project has no datafile yet, flags that use OIDC take the project from the project_id claim of the VERCEL_OIDC_TOKEN of vercel env pull, so Flags Explorer no longer fails until the first flag is created. Flags with an SDK key still throw. Updated dependencies [072184f, 9c5de4b]: @vercel/[email protected] [email protected]

    Original source
  • Nov 19, 2026
    • Date parsed from source:
      Nov 19, 2026
    • First seen by Releasebot:
      Nov 19, 2026
    • Modified by Releasebot:
      Nov 21, 2026
    Vercel logo

    Flags SDK by Vercel

    Flags SDK now rejects mismatched precompute codes and accepts the __no_flags__ sentinel only for empty flag arrays.

    Patch Changes

    #592 9c5de4b Thanks @luismyer!

    • deserialize and getPrecomputed now throw when a precompute code does not match the requested flags group, such as an empty-group code paired with a non-empty group (or the other way around). The __no_flags__ sentinel is now only accepted when deserializing an empty flags array.
    Original source
  • Similar to Flags SDK with recent updates:

  • Oct 30, 2026
    • Date parsed from source:
      Oct 30, 2026
    • First seen by Releasebot:
      Nov 3, 2026
    Vercel logo

    Flags SDK by Vercel

    Flags SDK adds a projectId option to prepare for upcoming Vercel Flags Project Connections.

    Minor Changes

    • #539 24983f9 Thanks @vincent-derks! - Prepare for upcoming Vercel Flags Project Connections with a new projectId option.
    Original source
  • Oct 30, 2026
    • Date parsed from source:
      Oct 30, 2026
    • First seen by Releasebot:
      Nov 3, 2026
    Vercel logo

    Flags SDK by Vercel

    @flags-sdk/[email protected]

    Flags SDK adds a projectId option to prepare for upcoming Vercel Flags Project Connections.

    Minor Changes

    #539 24983f9 Thanks @vincent-derks! - Prepare for upcoming Vercel Flags Project Connections with a new projectId option.

    Patch Changes

    Updated dependencies [24983f9]:

    Original source
  • Oct 28, 2026
    • Date parsed from source:
      Oct 28, 2026
    • First seen by Releasebot:
      Oct 29, 2026
    Vercel logo

    Flags SDK by Vercel

    Flags SDK now fails fast on authentication errors, revalidates reads over HTTP, and stops retrying polling without an OIDC token.

    Patch Changes

    #578 63d13be Thanks @luismeyer! - Fail fast on authentication errors. When the stream gets a 401 or no OIDC token is available, the client no longer falls back to polling, which would fail the same way, and goes straight to revalidating over HTTP on reads. When polling is the primary source, its first auth failure stops it, and a missing OIDC token is no longer retried. A failed OIDC token refresh is still retried. A client without credentials no longer keeps scripts and test files running.

    Original source
  • Oct 28, 2026
    • Date parsed from source:
      Oct 28, 2026
    • First seen by Releasebot:
      Jul 11, 2026
    • Modified by Releasebot:
      Nov 3, 2026
    Vercel logo

    Flags SDK by Vercel

    @flags-sdk/[email protected]

    Flags SDK updates its flags-core dependency to version 1.10.3.

    Patch Changes

    Updated dependencies [63d13be]:

    Original source
  • Oct 26, 2026
    • Date parsed from source:
      Oct 26, 2026
    • First seen by Releasebot:
      Oct 27, 2026
    Vercel logo

    Flags SDK by Vercel

    Flags SDK improves authorization error guidance and reads embedded flag definitions at client creation in SDK key or OIDC mode.

    Patch Changes

    • #567 5f738f0 Thanks @vincent-derks! - Improve guidance for authorization errors.
    • #573 e2a1a39 Thanks @luismeyer! - Read embedded flag definitions when the client is created, using the SDK key or VERCEL_PROJECT_ID in OIDC mode.
    Original source
  • Oct 26, 2026
    • Date parsed from source:
      Oct 26, 2026
    • First seen by Releasebot:
      Oct 27, 2026
    Vercel logo

    Flags SDK by Vercel

    @flags-sdk/[email protected]

    Flags SDK updates its dependencies to newer core and SDK versions.

    Patch Changes

    Updated dependencies [5f738f0, e2a1a39, c03fba8]:

    Original source
  • Oct 26, 2026
    • Date parsed from source:
      Oct 26, 2026
    • First seen by Releasebot:
      Oct 27, 2026
    Vercel logo

    Flags SDK by Vercel

    Flags SDK adds OpenTelemetry span emission in its SvelteKit adapter when a tracer provider is set.

    Minor Changes

    • #570 c03fba8 Thanks @kakadiadarpan! - Emit OpenTelemetry spans from the SvelteKit adapter when a tracer provider is set.
    Original source
  • Oct 20, 2026
    • Date parsed from source:
      Oct 20, 2026
    • First seen by Releasebot:
      Oct 21, 2026
    Vercel logo

    Flags SDK by Vercel

    Flags SDK adds config revision reporting to evaluation events, keeping usage data for different revisions separate.

    Patch Changes

    • #552 f02cc66 Thanks @luismeyer! - Report the flags config revision on FLAG_EVALUATION usage events, so evaluations can be broken down by the config revision that was served. Evaluations of different revisions are no longer merged into the same aggregated event.
    Original source
  • Oct 20, 2026
    • Date parsed from source:
      Oct 20, 2026
    • First seen by Releasebot:
      Oct 21, 2026
    Vercel logo

    Flags SDK by Vercel

    @flags-sdk/[email protected]

    Flags SDK updates its core dependency to version 1.10.1 in a patch release.

    Patch Changes

    Updated dependencies [f02cc66]:

    Original source
  • Oct 16, 2026
    • Date parsed from source:
      Oct 16, 2026
    • First seen by Releasebot:
      Oct 16, 2026
    Vercel logo

    Flags SDK by Vercel

    Flags SDK skips connected projects when definitions can’t be fetched, preventing build failures.

    Patch Changes

    • #553 bc7a562 Thanks @vincent-derks! - Skip connected projects whose definitions cannot be fetched instead of failing the build.
    Original source
Releasebot

Curated by the Releasebot team

Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.

Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.