Skip to content

Version Packages#284

Merged
dferber90 merged 1 commit intomainfrom
changeset-release/main
Mar 6, 2026
Merged

Version Packages#284
dferber90 merged 1 commit intomainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Feb 24, 2026

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@vercel/prepare-flags-definitions@0.1.0

Minor Changes

  • 96ba122: Initial release of @vercel/prepare-flags-definitions. Extracts the core flag definitions preparation logic from the Vercel CLI into a standalone, reusable package.

@vercel/flags-core@1.1.0

Minor Changes

  • 823bf78: Add CJS support

  • 722b0d0: - adds CONTAINS & NOT_CONTAINS comparators

    • adds case insensitive versions of all string based comparators
  • b70c2ea: This version of the SDK will no longer fall back to polling in case of streaming issues, and rely on the current in-memory version of the datafile instead, or fall back to the embedded datafile if no in-memory version is available.

    • Rename FlagNetworkDataSource to Controller (old name still exported as alias)
    • Rename FlagNetworkDataSourceOptions to ControllerOptions (old name still exported as alias)
    • Rename DataSource interface to ControllerInterface
    • Add optional revision field to DatafileInput

Patch Changes

  • a924044: Fix bug with inverted NOT_ONE_OF segment comparator

@flags-sdk/vercel@1.0.2

Patch Changes

  • 689b157: Move @vercel/flags-core from peerDependency to regular dependency. It is no longer necessary to install @vercel/flags-core for the common use case.

    If your app does not use @vercel/flags-core directly, you can remove it from your dependencies and do not need to make any code changes.

    In case your app imports @vercel/flags-core directly, you should pass your instance of the Vercel Flags client to avoid having multiple instances.

    import { createClient } from "@vercel/flags-core";
    import { createVercelAdapter } from "@flags-sdk/vercel";
    
    const vercelFlagsClient = createClient(process.env.FLAGS);
    const vercelAdapter = createVercelAdapter(vercelFlagsClient);
    
    export const exampleFlag = flag({
      key: "example-flag",
      adapter: vercelAdapter(),
    });
  • Updated dependencies [823bf78]

  • Updated dependencies [a924044]

  • Updated dependencies [722b0d0]

  • Updated dependencies [b70c2ea]

    • @vercel/flags-core@1.1.0

@vercel
Copy link
Contributor

vercel bot commented Feb 24, 2026

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

Project Deployment Actions Updated (UTC)
flags-sdk-dev Ready Ready Preview, Comment, Open in v0 Mar 6, 2026 10:16am
flags-sdk-next-15 Ready Ready Preview, Comment, Open in v0 Mar 6, 2026 10:16am
flags-sdk-next-16 Ready Ready Preview, Comment, Open in v0 Mar 6, 2026 10:16am
flags-sdk-snippets Ready Ready Preview, Comment, Open in v0 Mar 6, 2026 10:16am
flags-sdk-sveltekit-snippets Ready Ready Preview, Comment, Open in v0 Mar 6, 2026 10:16am
shirt-shop Ready Ready Preview, ✅ 1 resolved, Open in v0 Mar 6, 2026 10:16am
shirt-shop-api Ready Ready Preview, Comment, Open in v0 Mar 6, 2026 10:16am

@github-actions github-actions bot force-pushed the changeset-release/main branch from 7ec8276 to 6cdcace Compare February 25, 2026 08:56
@github-actions github-actions bot force-pushed the changeset-release/main branch from 6cdcace to 8648ac7 Compare February 25, 2026 08:57
@github-actions github-actions bot force-pushed the changeset-release/main branch from 946c422 to 9da806b Compare March 5, 2026 09:36
@github-actions github-actions bot force-pushed the changeset-release/main branch from 9da806b to 56ed2bb Compare March 5, 2026 09:53
@github-actions github-actions bot force-pushed the changeset-release/main branch from 56ed2bb to ab3c5f4 Compare March 5, 2026 11:53
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.

1 participant