Feature Flagging and Experimentation Release Notes
Release notes for feature flagging, A/B testing and experimentation platforms
Products (17)
Latest Feature Flagging and Experimentation Updates
- Jul 10, 2026
- Date parsed from source:Jul 10, 2026
- First seen by Releasebot:Jul 11, 2026
@vercel/[email protected]
Flags SDK improves flag bucketing by aligning rollouts, splits, and segment splits onto one shared hash scheme. This release keeps split assignments effectively unchanged and prevents user reassignment when converting between rollout and split outcomes.
Minor Changes
#427 50b1aa4 Thanks @dferber90! - Align rollout, split, and segment split user assignment onto a single hash bucketing scheme.
Previously splits and rollouts bucketed users with opposite conventions, so switching a flag between a split and a rollout (or locking in a rollout as a split) could reassign users even when the effective distribution was unchanged. All three now derive their cut points from one shared boundary function over the full hash space, so a rollout at a given percentage is identical to the equivalent split.
Split assignments are effectively unchanged. Rollouts and segment splits are re-bucketed once with this release; after that, converting a flag between outcome types never reassigns anyone.
Original source - Jul 10, 2026
- Date parsed from source:Jul 10, 2026
- First seen by Releasebot:Jul 11, 2026
@flags-sdk/[email protected]
Flags SDK ships patch updates with refreshed dependencies including @vercel/flags-core 1.7.0.
All of your release notes in one feed
Join Releasebot and get updates from Vercel and hundreds of other software products.
- Jul 10, 2026
- Date parsed from source:Jul 10, 2026
- First seen by Releasebot:Jul 11, 2026
@flags-sdk/[email protected]
Flags SDK adds native LaunchDarkly Marketplace integration and changes the default adapter to read the Edge Config connection string from EXPERIMENTATION_CONFIG, with a new error message and guidance for legacy Vercel setups.
Major Changes
#418 5488865 Thanks @mbrakken! - Support the native LaunchDarkly Marketplace integration.
Breaking changes:
The default adapter (
ldAdapter) now reads the Edge Config connection string from theEXPERIMENTATION_CONFIGenvironment variable instead ofEDGE_CONFIG. This aligns with the native LaunchDarkly Marketplace integration and matches the behavior of other adapters (e.g. Statsig).EDGE_CONFIGis no longer read by the default adapter. The error thrown whenEXPERIMENTATION_CONFIGis not set changed toLaunchDarkly Adapter: Missing EXPERIMENTATION_CONFIG environment variable.If you use the legacy LaunchDarkly Vercel integration (which provides the connection string as
EDGE_CONFIG), pass the connection string explicitly withcreateLaunchDarklyAdapter:
Original sourceimport { createLaunchDarklyAdapter } from "@flags-sdk/launchdarkly"; const ldAdapter = createLaunchDarklyAdapter({ projectSlug: process.env.LAUNCHDARKLY_PROJECT_SLUG, clientSideId: process.env.LAUNCHDARKLY_CLIENT_SIDE_ID, edgeConfigConnectionString: process.env.EDGE_CONFIG, }); - Jul 8, 2026
- Date parsed from source:Jul 8, 2026
- First seen by Releasebot:Jul 9, 2026
Rebuilding the GrowthBook Visual Editor
Growthbook introduces a rebuilt AI-first Visual Editor that helps teams launch A/B tests faster with browser-side editing, image generation, Figma and mockup import, durable selectors for modern sites, no-flicker support, multilingual UI, and transparent change review.
Visual editors are a staple of experimentation platforms. The promise is simple: let anyone change a website and launch an A/B test without writing code or waiting on engineering. In practice, most visual editors fall short. They break on modern sites, cause flicker, and quietly push you back into writing CSS or HTML the moment anything gets tricky.
We designed the GrowthBook Visual Editor from a blank slate to fix these issues. The result is an AI-first editor that lives in your browser's side panel, and it finally lives up to the full potential of a visual editor. This post walks through what is new and why each piece matters for running A/B tests without engineering overhead.
AI first
Most visual editors are visual right up until they are not. The moment you need to nudge spacing or fix a layout, you are back in a CSS box. GrowthBook’s visual editor moves the editing into an AI prompt by default, so any change you can describe, you can build.
Ask it to change the background color, rewrite a headline, generate a few alternative CTAs, or restyle a section. The editor applies the change on the page instantly, and you approve it, reject it, or ask for something different. Nothing is saved to your variation until you accept it.
The AI also reads the live page, including the real elements and their computed styles, so its suggestions are grounded in your actual site rather than guesses. If it is unsure which section you mean, click to select one or more elements and the prompt uses them as context.
AI image editing and generation
Images are often the highest-impact thing to test and the hardest to change without a designer. GrowthBook builds image editing and generation directly into the editor.
Ask the AI to generate a brand new image from a description, replace an existing image, or produce variations based on the image already on the page. Generated images are automatically cropped to the exact dimensions of the slot they replace, so nothing stretches or distorts. You can generate several options at once and pick the one that fits.
Import from Figma or a mockup
Designs usually start in Figma or as a static mockup, and getting them into an experiment has meant a manual rebuild. GrowthBook can import directly from either.
Connect your Figma account and point the editor at a frame, or hand it an image of the design you want. It analyzes the design and turns it into a variation you can preview and refine, so a mockup can become a running test without rebuilding it by hand. You can also add additional context about how you want the design implemented.
Built for modern web platforms
This is where most visual editors quietly fail. Modern frameworks and site builders generate class names like
css-1x9f3kthat change on every deploy. A visual editor that targets those names will silently break the next time your site ships, and the experiment stops running with no warning.
GrowthBook builds durable selectors instead. It ignores hashed and build-generated class names, prefers stable attributes, and anchors to elements in a way that survives redeploys. Your variations keep working after the next release.
Manual mode and global code
When you want precise control, manual mode gives you a full WYSIWYG editor for any element you pick. Edit text, typography, layout, background, visibility, and classes, with each control pre-filled to the element's current values so you are adjusting from where the page actually is. This is also where the most advanced image editor lives. Select any img element to see the options. For changes that span the whole variation, the global CSS and JavaScript editors let you drop in custom code without leaving the panel (or let the AI generate this for you).
No flicker
Flicker is the flash of original content that appears before a variation loads, and it is one of the fastest ways to bias an experiment. GrowthBook avoids it by applying changes before the page renders. Serve the GrowthBook SDK and your feature definitions from your own CDN or edge, and the variation is applied on the initial render rather than after it. Visitors see the variant immediately, with no flash of the control. If you don’t use a CDN, you can still enable the usual no-flicker scripts. See the
docs on avoiding flicker
for setup.
Edit in 4 languages, and even in dark mode
The editor speaks more than English. Switch the interface into German, Spanish, or Portuguese so teams outside English-first organizations can work in their own language. And if you prefer a darker workspace, dark mode is one click away.
Complete transparency
Every change the editor makes is listed in one place. You can see each edit, preview it on or off, jump straight to the affected element on the page, and edit or delete anything you no longer want. Nothing happens in a black box. You can also test your targeting before launch: the built-in URL tester tells you whether a specific URL would be included in the experiment, using the exact same logic the SDK uses in production.
Try it out!
The rebuilt GrowthBook Visual Editor is AI-first, works on modern sites, and keeps you in control of every change. It makes launching an A/B test faster for everyone on the team, not just the people who write CSS. Get started with GrowthBook to create your first visual experiment, or read the
visual editor docs
to see how it fits your setup.
Original source - Jul 8, 2026
- Date parsed from source:Jul 8, 2026
- First seen by Releasebot:Jul 9, 2026
@vercel/[email protected]
Flags SDK adds aggregated flag evaluation telemetry and a clientName option for the Vercel Flags client.
Minor Changes
#401 9dff590 Thanks @luismeyer! - Add aggregated flag evaluation telemetry and a clientName option for the Vercel Flags client.
Original source - Jul 7, 2026
- Date parsed from source:Jul 7, 2026
- First seen by Releasebot:Jul 8, 2026
🔬 Experiment Reviews via Console API and MCP
Statsig expands the experiment review lifecycle in the Console API and Statsig MCP, adding end-to-end support for creating, approving, rejecting, editing, canceling, and committing reviews so teams can manage review-gated experiment changes without the console.
The full experiment review lifecycle is now accessible over the Console API and the Statsig MCP.
What you can do now
We now have eight new CAPI endpoints and niine new MCP tools cover the complete review lifecycle:
- Create a review proposing a change to an experiment
- List an experiment's reviews, newest first
- Get a single review including status, proposed change, author, and reviewers
- Look up who is eligible to approve or reject
- Edit a pending review's metadata
- Approve or reject an in-flight review
- Cancel a pending review
- Commit an approved review to apply it to the live experiment
Why this matters
Before, creating and moving an experiment review through approval required the console, blocking any automated workflow that touched a review-gated experiment. Now you can propose, approve, and commit experiment changes entirely through the API or MCP, with no manual console step in the way.
Try it out
If you have the Statsig MCP set up, try a prompt like:
"Open a review to make a decision on
experiment_name
, shipping the Test group."Review the full API reference in the
Original source
Statsig Console API docs
. - Jul 7, 2026
- Date parsed from source:Jul 7, 2026
- First seen by Releasebot:Jul 8, 2026
🔎 Audit Overrides
Statsig adds project-wide override auditing with a new Console API endpoint, letting teams query all overrides in a single call for faster debugging, compliance checks, and cleanup.
🔎 Audit Overrides Across Your Entire Project
You can now query all overrides across your project in a single API call.
What you can do now
We now have one new endpoint available on statsigapi.net/console/v1/ :
GET /console/v1/overrides
Why this matters
Before , finding where a user was overridden meant querying each gate, experiment, and layer one by one. Now you can audit overrides project-wide in a single call, whether you're debugging unexpected behavior for a specific user, running a compliance audit, or cleaning up override sprawl.
Try it out
Review the full API reference in the Statsig Overrides Audit docs.
Original source - Jul 7, 2026
- Date parsed from source:Jul 7, 2026
- First seen by Releasebot:Jul 7, 2026
Monthly Release Notes - June 2026
Convert.com adds Android and iOS SDKs plus Python and Ruby SDKs to expand native full-stack experimentation across mobile and backend apps. It also brings Version Control to the Visual Editor and adds a GA4 setting to track first visitor exposure only for cleaner impression tracking.
Android SDK Now Available for Native App Experimentation
We launched the Android SDK, making it easier for mobile teams to run experiments and deliver consistent testing experiences directly inside their Android applications.
This gives Android teams a native way to adopt full-stack experimentation, feature delivery, and conversion tracking within the app experience. More here: Android Quickstart
iOS SDK Released for Full-Stack Testing in Apple Apps
We launched the iOS SDK, giving iOS developers a seamless way to implement full-stack experimentation directly in their applications.
With native support for running experiences and tracking conversions inside iOS apps, teams can now extend experimentation more naturally across Apple platforms. More here: iOS Quickstart
Python SDK Released for Backend Experimentation
We released the Python SDK, enabling backend teams to integrate feature experimentation and full-stack testing more naturally into their Python services.
This gives Python-based teams a more native path to server-side decisioning and experimentation as part of their existing application workflows. More here: Python Quickstart
Ruby SDK Now Available for Full-Stack Testing
We released the Ruby SDK, allowing Ruby developers to adopt full-stack testing with a solution that fits naturally into their existing workflows.
This makes it easier to run server-side experiments, feature flags, and conversion tracking from Ruby applications without forcing teams into unfamiliar tooling. More here: Ruby Quickstart
Version Control Added to the Visual Editor
We introduced Version Control in the Visual Editor, adding recovery and restore capabilities to help prevent lost work.
This is especially useful when multiple collaborators are editing the same variation, since users can now restore previous or preferred changes more easily without having to redo their work. More here: Version Control
New “Track First Visitor Exposure Only” Setting for GA4
We introduced Track first visitor exposure only for the GA4 integration.
When enabled, Convert sends the experience_impression event only the first time a visitor is exposed to a specific experience, instead of firing the same impression repeatedly on later qualifying page views. This helps reduce duplicate impression events and makes exposure tracking cleaner for analysis in GA4. More here
Original source - Jul 3, 2026
- Date parsed from source:Jul 3, 2026
- First seen by Releasebot:Jul 4, 2026
v2.252.0
Flagsmith adds onboarding, experimentation, and segment membership improvements, including prompts for required integrations, Flagsmith-on-Flagsmith organisation traits, and a better rollout change experience, while also fixing several segment, subscription, and usage issues.
2.252.0 (2026-07-03)
Features
- code-references: prompt users to add required integrations (#7844) (27e76f0)
- Flagsmith-on-Flagsmith: Send organisation trait to Flagsmith on identify (#7932) (0bc9f7a)
- improve experiment recommendation and disable Snowflake warehouse (#7940) (31c9dc9)
- onboarding: connection terminal and flags table (#7856) (ece3b36)
- Segment Membership: Recount after identity delete (#7933) (b8b25c1)
Bug Fixes
- experimentation: rebuild environment document on rollout change (#7929) (c9a5f54)
- organisation: disable delete button when active subscription exists (#7809) (44206a2)
- Segment Membership: Oversized numeric traits fail identity seeding (#7938) (cbc295a)
- Segment Membership: Percent sign in regex condition crashes segment count refresh (#7944) (e77c851)
- Segment Membership: Stagger the recurring count refresh fan-out (#7943) (9105ae0)
- usage: Send raw licence signature bytes in Control Plane auth token (#7936) (6849e3f)
Dependency Updates
- api: Bump flagsmith-sql-flag-engine to 0.1.3 (#7935) (946df88)
Docs
- integrations: Split Grafana and Prometheus integration pages (#7921) (d80e457)
- Jul 3, 2026
- Date parsed from source:Jul 3, 2026
- First seen by Releasebot:Jul 4, 2026
@vercel/[email protected]
Flags SDK adds fetch retries in Minor Changes #421, improving reliability.