This page provides a high-level summary of releases starting from 2025. It details new functionality, UI changes, deprecations, and important announcements across Unleash and its components.
How to use the tags
Each release note is tagged with the part of the product it applies to. Use the tags to filter for the areas you’re interested in.
- Unleash: The core platform, including the Unleash server, the Admin UI, and overarching product decisions and announcements. See the architecture overview.
- Enterprise Edge: Releases for Unleash Enterprise Edge, a lightweight caching layer that improves the scalability, performance, and resilience of your feature flag infrastructure.
- MCP server: Releases for the Unleash MCP server, which lets AI coding assistants manage feature flags.
- SDKs: Changes that affect the Unleash SDKs, such as naming changes or new capabilities that span multiple SDKs.
A single release note can carry more than one tag when a release touches several areas.
Versioning
Unleash follows semantic versioning, with major versions (for example, v7.0.0) including significant new features and might include breaking changes, and minor versions (for example, v7.4.0) adding new functionality while maintaining backward compatibility.
For a comprehensive list of all Unleash releases, including patch versions and history prior to 2025, visit the Unleash Releases page on GitHub.
The Unleash MCP server, Unleash Enterprise Edge, and each SDK are versioned independently and publish their own changelog in their respective GitHub repositories.
Unleash v7.1.0
Feature flag lifecycle improvements
You can now mark any flag as Ready for cleanup, even if it never reached production. This helps you clean up flags at any stage in the lifecycle, for example, a kill switch you never enabled in production, and reduce technical debt.
We also renamed Health to Technical debt to align with common engineering terminology. In Project > Project status, you can see a technical debt rating for the project. In Analytics > Technical debt, you can explore the same data at the instance and project levels.
Renamed SDKs and token types
We’ve introduced a more consistent naming pattern for our SDKs and API tokens. Server-side SDKs are now backend SDKs, and client-side SDKs are frontend SDKs. Backend SDKs use backend tokens and frontend SDKs use frontend tokens.
You’ll find the new naming across our documentation and in the Admin UI, such as when creating API tokens or working with permissions. We also standardized SDK repository and registration names to follow the unleash-{language/framework}-sdk pattern. For example, unleash-client-python has been renamed to unleash-python-sdk. Note that SDK artifact names remain unchanged to avoid requiring changes to your codebase.
Grouped events in Event Log
Event Log now marks related events using a Group ID when a single action produces multiple changes. This makes the full sequence of changes easier to trace and audit.
For example, when a change request is approved and applied, all resulting events, such as strategy or flag config changes, appear under the same Group ID. Similarly, if enabling a flag in an environment automatically adds the default strategy, both events share the same Group ID to reflect that they came from the same action.
In addition, we’ve made the date filter optional and added filtering by ID on the Events API.
View connected frontend applications
To help debug frontend application connections, you can now view connected frontend applications inside Configure > Applications and in each project’s Applications tab. If an application uses both backend and frontend SDKs, both are shown on the application’s overview page.