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.5.0
User groups with root roles can now be assigned to projects
Previously, groups with a root role could not be added to projects in the Admin UI. This restriction has been removed. You can now add any group to a project regardless of whether it has a root role. This is especially useful for teams that sync groups from SSO providers, as it removes the need to maintain separate groups for root-level and project-level access.
API access URLs for Edge
You can now copy the Edge URLs directly from Admin settings > Access control > API access. For hosted customers, this works automatically. If you are self-hosting, you can configure the EDGE_URL environment variable on startup to ensure the right endpoints are visible in the UI.
Fixed scoping for private project data
We fixed how private projects scope visibility within your organization. Previously, users who weren’t added to a private project could still see some of its metadata, like segments, in global views. Affected views and endpoints now correctly return 404.
Announcement: Automated release management and Unleash MCP in beta
Two new capabilities are now available in beta.
Impact Metrics are lightweight, application-level time-series metrics you can track and visualize right inside Unleash. Counters, gauges, and histograms for things like error rates, latency, and adoption feed directly into release templates, so Unleash can automatically progress a rollout when signals are healthy or pause it when something spikes.
Impact Metrics are currently enabled for select customers. If you’d like to enable it for your organization, reach out to beta@getunleash.io.
We’ve also launched the Unleash MCP server in beta. This gives your AI coding assistants a structured contract for managing feature flags safely. It plugs into tools like Claude Code, Cursor, Windsurf, and Codex, and guides them through evaluating risk, creating flags, wrapping code, and cleaning up after rollout.