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.6.0
Project-level context fields
Context fields can now be defined at a per-project level. To create one, open a project and go to Settings > Context fields. Once you define project-level context fields, they are available in strategy configuration and the playground for users with access to that project, but are not included in the global context fields overview.
Edit strategies in applied release plans
You can now edit activation strategies in a release plan after the release template is applied to a feature flag. You can edit the configuration, constraints, variants, rollout percentage, or set the status to Inactive, just as you would with any standalone strategy.