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
- Apr 14, 2026
- Date parsed from source:Apr 14, 2026
- First seen by Releasebot:Apr 15, 2026
- Apr 14, 2026
- Date parsed from source:Apr 14, 2026
- First seen by Releasebot:Apr 14, 2026
v2.228.0
Flagsmith releases OAuth consent screen updates, dynamic client registration, and OpenTelemetry support for the Task Processor. It also adjusts billing with a restored Scale-Up plan and capped seats, alongside bug fixes and docs improvements.
2.228.0 (2026-04-14)
Features
- backend-oauth-consent-screen (#7124) (0e985d9)
- Billing: Cap Scale-Up seats at 20 (#7217) (c3c837a)
- Billing: Reintroduce the Scale-Up plan (#7216) (556b114)
- Enable OpenTelemetry support for Task Processor (#7225) (8dd8c46)
- implement dynamic client registration (#7096) (8cd740f)
- oauth-consent-frontend-screen (#7136) (643682d)
- open-api-specs-describe-oauth (#7148) (97bb4f4)
- setup-dot-and-metadata-endpoint (#7057) (58f6e51)
- support DJANGO_DB_CONN_HEALTH_CHECKS for persistent DB connections (#7220) (9e92fbd)
- visual regression e2e (#7102) (fccd6db)
Bug Fixes
- compress_dynamo_documents breaks permanent environment cache (#7014) (b5f81bc)
- account-dropdown: fix contrast issues in dark mode (#7088) (c924459)
- Add index.handlebars to vercel include files (#7191) (0bad5b2)
- ci: improve Chromatic workflow (#7156) (db4e578)
- drop stale DB connections around LaunchDarkly fetch phase (#7219) (7f219c0)
- e2e: skip SDK keys test when feature flag is off (#7155) (807185b)
- environments: validate project field in environment creation (#7063) (f4c5f66)
- return null instead of empty string when clearing feature value (#7146) (7ece5ea)
- storybook dark mode and component compatibility (#7209) (a7242c2)
- tests: Use unique email in flaky custom auth integration test (#7113) (b4cf014)
- v1-override-limit-includes-all-feature-segments-in-count (#6555) (c5af2d5)
Dependency Updates
- bump cryptography from 46.0.6 to 46.0.7 in /api (#7187) (de527ae)
- bump django from 5.2.12 to 5.2.13 in /api (#7186) (1ecf480)
- upgraded-axios (#7218) (de45b91)
CI
- pre-commit autoupdate (#7141) (d604cd0)
- skip-private-tests-and-comments-conditionally-for-oss-contributions (#7189) (9e3edac)
Docs
- fix edge proxy API URL reference to use edge.api.flagsmith.com (#7152) (68f851a)
- OpenTelemetry (#7103) (7beff52)
- Update GCP self-hosting to recommend GKE with Helm charts (#7177) (b34f718)
Refactoring
- AccountSettingsPage TypeScript migration (#7169) (c1aef00)
- CJS -> ESM (#7178) (91558ce)
- Codehelp TypeScript migration (#7170) (9dcde58)
- Migrate users urls+page names to Identities (#7168) (e122a95)
- modernise Payment modal (#7004) (7d2f132)
- modernise Server-side SDK Keys page (#7003) (4e5fa9f)
- Move icons, remove unused files (#7171) (589c5d5)
All of your release notes in one feed
Join Releasebot and get updates from Vercel and hundreds of other software products.
- Apr 14, 2026
- Date parsed from source:Apr 14, 2026
- First seen by Releasebot:Mar 12, 2026
- Modified by Releasebot:Apr 15, 2026
@flags-sdk/[email protected]
Flags SDK adds progressive rollout outcome and updates dependencies.
Minor Changes
80dcdad: Add progressive rollout outcome
Patch Changes
Updated dependencies [80dcdad]
@vercel/[email protected]
Original source - Apr 13, 2026
- Date parsed from source:Apr 13, 2026
- First seen by Releasebot:Apr 16, 2026
April 13, 2026
Dynamic Yield now serves overlays and notifications to non-consenting users when they don’t rely on personal targeting or frequency settings.
If you enabled Active Cookie Consent, you can now serve overlays and notifications for users to users who did not provide consent, if overlays and notifications does not rely on personal targeting or frequency settings.
Original source - Apr 8, 2026
- Date parsed from source:Apr 8, 2026
- First seen by Releasebot:Apr 8, 2026
Version 4.38.1
ABTasty fixes event tracking for Recos and Merch so the latest data reaches the data layer accurately.
AI Generated Release Note
Bug Fixes
- Event Tracking Fix for Recos & Merch: Fixed an issue ensuring that the latest data is accurately sent to the data layer.
- Apr 8, 2026
- Date parsed from source:Apr 8, 2026
- First seen by Releasebot:Apr 8, 2026
Version 4.38.0
ABTasty improves the Modification Engine with dynamic bundling, consented Wandz.ai integration, and event tracking fixes.
AI Generated Release Note
Improvements
- Dynamic Bundling: The Modification Engine now uses dynamic bundling by default, improving system efficiency and responsiveness.
- Enhanced Integration for Wandz.ai: Ensure Wandz.ai tag is injected with user consent, enhancing user control over integrations.
Bug Fixes
- Event Tracking Fix for Recos & Merch: We’ve changed the way events are sent to the data layer, which resolves previous tracking issues and ensures accurate data collection.
- April 2026
- No date parsed from source.
- First seen by Releasebot:Apr 7, 2026
Restoring previous flag versions
LaunchDarkly adds the ability to restore a feature flag to a previous version from change history, with code diffs, previews, and safeguards for identical versions and older or restricted states.
Overview
This topic explains how to use the change history tab to restore a feature flag to a previous version.
Flag versions in change history
You can change a feature flag to a previous version.
Versions increment based on your actions. For example, if you are on version 5 and restore version 3, version 3 is brought forward and becomes version 6. The restore workflow shows version numbers, code diffs, and a preview of the new version. You cannot restore a version that is identical to the current version. If you try to restore an identical version, the diff is abbreviated to only show the updated timestamps and version numbers, and restoring is disabled.
To restore a previous version, visit the change history page.
Limitations
Flag versions are limited to flag configuration changes in the current environment, not flag variations or global flag settings. There are additional restrictions if a flag is part an experiment, rollout, or scheduled change. Here is a list of limitations for restoring previous flag versions:
- You can only restore states that existed within the last 30 days
- You can’t restore a version with an expired target date. For example, if the current date is June 1, 2026 and you attempt to restore a version that had a change scheduled to take effect on May 25, 2026, you cannot restore this version because the date of the scheduled change has already passed.
- You can’t roll back to states controlled by experiments, guarded rollouts, or progressive rollouts
Restore a previous flag version
Here’s how to restore a previous flag version:
- Navigate to the flag’s change history page and find the version you want to restore. Versions that can be restored are indicated with a button that has “Restore previous version” hover text.
- Click the version restore button in the row for the version you wish to restore. A code diff appears showing the changes between the current version and the version you intend to restore.
- Verify that the changed version does what you expect and click Stage this version. A preview appears.
- Click Review and save. A confirmation dialog appears.
- Type the environment’s name to confirm and click Save changes.
The earlier flag version is now the current version.
Original source - Apr 6, 2026
- Date parsed from source:Apr 6, 2026
- First seen by Releasebot:Apr 6, 2026
v2.227.0
Flagsmith adds OpenTelemetry support and fixes a PermissionsTabs crash before projects load.
2.227.0 (2026-04-06)
Features
- Enable OpenTelemetry support (#7132) (71968be)
- implement-gram-elements (#7049) (87fde45)
Bug Fixes
- frontend: avoid PermissionsTabs crash before projects load (#6993) (f9ec265)
- pinned-flagsmith-to-exact-version (#7119) (864ab75)
Dependency Updates
- bump minimatch and serve-handler in /docs (#7118) (3bef311)
Docs
- Update go client version in docs and code help (#6954) (723d77c)
- Apr 3, 2026
- Date parsed from source:Apr 3, 2026
- First seen by Releasebot:Apr 3, 2026
Flags SDK improves Next.js flag evaluation performance with caching and lower microtask overhead.
Patch Changes
c08f3e5: Improve performance by caching next/headers imports. Previously every flag evaluation in Next.js App Router would run await import("next/headers"). The imported module is cached by the runtime, but we would still go through the event loop unnecessarily. Now we cache the resolved module in a local variable so only the first call awaits the dynamic import; subsequent calls skip the microtask entirely.
c08f3e5: Reduce microtask queue overhead in flag evaluation by replacing the async IIFE around decide() with a direct call and Promise.resolve().
- Apr 3, 2026
- Date parsed from source:Apr 3, 2026
- First seen by Releasebot:Apr 3, 2026
Move beyond individual wins. Understand the true impact of your feature releases.
VWO introduces Holdouts for Feature Experimentation, giving teams a stable baseline to measure the true impact of feature rollouts, experiments, and personalization across the full roadmap. It helps compare visitors, conversions, and primary metrics to reveal real business lift.
Your checkout team ships a winner. Your search team launches a hit.
The individual test reports are glowing green, but when the quarterly review hits, you see little to no impact on your revenue.Why? Because your “winning” updates might be silently colliding, and there’s no way to know if they are.
You are left wondering:
“Is our product roadmap ‘actually’ delivering the impact?”Enter Holdouts.
Now you can exclude a small, intentional subset of your traffic from a series of new feature rollouts, experiments, and personalization campaigns, over weeks, months, or quarters.
This subset acts as a pure, stable baseline and represents exactly what user behavior would look like if you didn’t deploy any product changes.How to use Holdouts?
Setting up a Holdout in VWO is seamless and fits right into your existing workflow. By associating a holdout with your feature flags, it universally works across all your feature rollouts, personalizations, and experiments.
We offer two types of Holdouts:
Global Holdouts: Automatically exclude your Holdout users from all new feature flags across your product to measure your entire roadmap’s impact.
Selective Holdouts: Manually associate specific feature flags to your Holdouts to measure the combined impact of a specific theme or initiative.
Once active, you get a definitive, dashboard-level view comparing total visitors, conversions, and primary metric values between the Holdouts and users bucketed in your campaigns overall.
How does it help your industry?
For E-commerce & Retail:
Imagine you launch guest checkout, revamp your recommendation algorithm, introduce an enhanced search experience, revamp the product listing page, and evolve the search experience, all in a single quarter. Individual A/B tests for each, can’t prove the cumulative bottom-line impact. By keeping a set of users that are isolated from these releases, you get scientific proof about these releases, whether they are even increasing your conversions, AOV, or revenue.
For SaaS & Software:
Move the conversation from “Did a specific onboarding change win?” to “Did our Q3 product roadmap actually increase user retention and Customer Lifetime Value?” You finally have the data to prove your strategy works.
For News & Media:
If you launch a new personalization algorithm for the news feed, a metered paywall, and start testing a new ad platform, make a few UI/UX changes, and revamp article writing style, in a single quarter. Such individual A/B tests can’t prove cumulative impact on engagement & revenue. By having the Holdout users as your original baseline, you get a clear indication of the impact of your launches.
Why is this important to you?
Justify your product investments and illustrate ROI:
Solve your leadership’s biggest struggle: “Tangibly understanding the ROI of product development.” Deliver a data-backed analysis to prove exactly how your development efforts are impacting key business goals.Proactively detect anomalies and course-correct:
Get an early warning if your recent series of improvements is actually causing unintended harm and trending negatively. This allows your team to intervene and course-correct before long-term damage occurs.Set a culture of true accountability:
Use Holdouts to bring transparency and align your teams towards one common vision, by tying feature launches directly to business health. You shift your team’s mindset from simply shipping features to actually driving business outcomes.Start visualizing your true roadmap ROI today!
Holdouts are currently available for the Enterprise Plan (Early access) of VWO Feature Experimentation. Please reach out to your Customer Success Manager to get access.
To know more, head over to our Knowledge Base.
If you have any questions or feedback, we are all ears at [email protected].
Original source