> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.getunleash.io/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.getunleash.io/_mcp/server. # Release notes > Review Unleash release notes from 2025 onward, covering new features, UI updates, deprecations, and major changes across the platform, Enterprise Edge, the MCP server, and SDKs. 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](/get-started/unleash-overview). * **Enterprise Edge**: Releases for [Unleash Enterprise Edge](/unleash-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](/integrate/mcp), which lets AI coding assistants manage feature flags. * **SDKs**: Changes that affect the [Unleash SDKs](/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](https://github.com/Unleash/unleash/releases) page on GitHub. The [Unleash MCP server](/integrate/mcp), [Unleash Enterprise Edge](/unleash-edge), and each [SDK](/sdks) are versioned independently and publish their own changelog in their respective GitHub repositories. ## September 8, 2026 > Review Unleash v8.2.0 release notes, covering project-level release templates, in-app notifications for access requests, the New in Unleash page in Open Source, and filtering flags by creator. # Unleash v8.2.0 ## Project-level release templates You can now create [release templates at the project level](/concepts/release-templates#create-a-project-level-release-template), in addition to creating them globally. Project-level templates are available only within the project they belong to, so teams can manage the templates for their own projects, while global templates remain available across the whole instance. ## New in Unleash page for Open Source The **New in Unleash** page is now also available in [Unleash Open Source](/support/availability#plans). It shows the latest capabilities added to Unleash and indicates which of them are Enterprise features. From the page, you can get started with a feature, read more in the documentation, request access to beta features, and see what we are working on next. You can find it in the **Help & Resources** menu in the top navigation. ## Filter flags by creator The flags overview now includes a [Created by filter](/concepts/search-operators#filter-feature-flags), so you can filter flags by the user who created them. ## August 5, 2026 > Review Unleash v8.1.0 release notes, covering an improved projects overview, streamlined flag lifecycle and archive views, context field cloning, impact metric creation from the UI, a new help menu, the ServiceNow integration in beta, and OpenFeature providers in beta. # Unleash v8.1.0 ## Improved projects overview The projects page now gives you a quicker overview of the status of your [projects](/concepts/projects). Project cards surface anything that needs your attention, such as pending [change requests](/concepts/change-requests), remaining setup steps, flags that are ready to be cleaned up, and [safeguards](/concepts/impact-metrics#configure-safeguards) that have been triggered, so you can act without opening each project. ## Streamlined flag lifecycle and archive views It is now easier to follow how flags move through their entire [lifecycle](/concepts/feature-flags#feature-flag-lifecycle). You can switch between the different lifecycle phases, including archived flags, in one cohesive view instead of navigating to several places to find flags in different phases. ## Clone context fields You can now [clone a context field](/concepts/unleash-context#clone-a-context-field) from the context field list, both in the global admin view and in project settings. Cloning opens the create form pre-filled with the source field's description, legal values, and stickiness, so you can quickly recover from a typo in a context field name or create a similar field without retyping a long list of legal values. ## Create impact metrics from the UI You can now [create an impact metric directly in the Admin UI](/concepts/impact-metrics#create-a-metric-from-the-ui). On the feature flag page, click **Add impact metric** in the impact metric banner. Previously, metrics could only be defined in code through an SDK. ## New help menu The top navigation has a new help menu that gathers useful links in one place: the [Unleash Learning Lab](/learning-lab/introduction), what is new in Unleash, documentation, GitHub, feedback, and the Slack community. Several of these links previously lived in the footer and are now easily accessible from anywhere in the Admin UI. ## ServiceNow integration in beta The new [ServiceNow integration](/integrate/servicenow) automatically tracks the state of your Unleash [change requests](/concepts/change-requests) in ServiceNow, giving you an audit trail of changes that are created, approved, and applied in Unleash. ## OpenFeature providers in beta We released new [OpenFeature providers](/sdks#openfeature-providers). These let you evaluate your feature flags through the vendor-neutral [OpenFeature](https://openfeature.dev/) API while continuing to manage them in Unleash. ## June 9, 2026 > Review Unleash v8.0.0 release notes, covering the move to AGPLv3, automated release management becoming generally available, the remote MCP server becoming generally available, streaming between Unleash and Edge in beta, improved project onboarding, a redesigned user access overview, and the new sunset flag type. # Unleash v8.0.0 If you self-host Unleash, review the [v7 to v8 migration guide](/deploy/upgrading-unleash#upgrading-from-v7-to-v8) before you upgrade. No API endpoints were removed, but several deprecated schema properties have been. ## Announcement: Unleash open source moves to AGPLv3 Starting with Unleash v8, the source code in the [primary Unleash GitHub repository](https://github.com/Unleash/unleash) and the [`unleash-server` npm package](https://www.npmjs.com/package/unleash-server) move from the Apache 2.0 license to the GNU Affero General Public License v3 (AGPLv3). Most users are unaffected: * Official open-source Docker images remain under Apache 2.0. Running a pre-built Unleash container without modifying the source is unaffected. * Unleash SDKs keep their current permissive licenses, so your application code is unaffected. * Unleash Enterprise and Unleash Cloud are unaffected. Your deployment, terms, and obligations are unchanged. The change applies if you modify the Unleash source and make it available to users over a network, for example as a public or commercial SaaS. In that case, AGPLv3 requires you to make your modified source available under the same license, or to contact us for a commercial license. For the full reasoning and a use-case breakdown, see [Evolving our open source commitment](https://www.getunleash.io/blog/unleash-moving-to-agplv3). ## Automated release management now generally available [Release templates](/concepts/release-templates), [impact metrics](/concepts/impact-metrics), [safeguards](/concepts/impact-metrics#configure-safeguards), and [milestone progression](/concepts/impact-metrics#automate-release-progression) are now generally available. Impact metrics are application-level time series, such as counters, gauges, and histograms for error rates, latency, and adoption. They can be recorded by Unleash SDKs or queried from an existing Prometheus or VictoriaMetrics instance. Safeguards let you set thresholds on those metrics that automatically pause a rollout or disable an environment when a metric crosses the limit. Milestone progression advances a release template to its next milestone when the metrics stay healthy for a configured interval, removing the need to step rollouts forward manually. ## Remote MCP server now generally available The [remote Unleash MCP server](/integrate/mcp#remote-mcp-server) is now generally available. It lets you connect MCP clients to a server hosted by your Unleash instance, without installing anything locally. Use it when developers cannot run MCP servers on their machines, or when you want to manage MCP access centrally. ## Streaming between Unleash and Edge in beta [Unleash Edge](/unleash-edge) can now receive flag updates from Unleash as a real-time stream instead of polling. Flag changes propagate to your Edge nodes, and to your applications, in milliseconds. Streaming is available on both managed and self-hosted [Enterprise Edge](/unleash-edge#real-time-updates-with-streaming). ## Improved project onboarding We've further improved the project onboarding experience. The project page now shows a three-step **Project setup** checklist that tracks creating a feature flag, connecting one or more SDKs, and sending flag evaluation metrics back to Unleash. On the flag page, a contextual banner points you to the next step based on your current setup state. SDK setup now also works for any SDK you add to a project, not only the first one. ## Redesigned access overview The [access overview page](/concepts/rbac#view-a-users-roles-and-permissions) is redesigned to give admins and individual users a clearer view of a user's instance and project access in one place. ## New `sunset` flag type We introduced a new `sunset` [flag type](/concepts/feature-flags#feature-flag-types) to help you coordinate the planned removal of an existing feature. Use it to wrap a feature you plan to retire, so you can gradually disable it for selected user segments while monitoring the impact, and pause or re-enable the rollout if downstream issues surface. ## May 26, 2026 > Review the Unleash MCP server v0.3.0 release notes, covering general availability, the remote MCP server in beta, and new flag and project discovery tools. # MCP server v0.3.0 ## Unleash MCP server is now generally available The [Unleash MCP server](/integrate/mcp) is now generally available. It gives your AI coding assistants a structured contract for managing feature flags safely, guiding them through evaluating risk, creating flags, wrapping code, and cleaning up after a rollout. It works with tools like [Claude Code](/integrate/claude-code), [Cursor](/integrate/cursor), [GitHub Copilot](/integrate/github-copilot), [Kiro](/integrate/kiro), and [OpenCode](/integrate/opencode). ## New tools to list flags and projects Two new tools let assistants discover and audit your feature flags directly: * `list_projects` lists all Unleash projects available to your token. * `list_flags` lists the feature flags in a project, with support for filtering, ordering, and pagination. These tools power agentic flag-audit workflows and back the `detect_flag` inventory analysis, so assistants can enumerate flags before creating new ones or identify cleanup candidates. For details, see the [tool reference](/integrate/mcp#tool-reference). ## Remote MCP server in beta You can now connect MCP clients to a [remote MCP server](/integrate/mcp#remote-mcp-server) hosted by your Unleash instance, without installing anything locally. This is useful when developers cannot run MCP servers on their machines, or when you want to manage MCP access centrally. The remote MCP server is in beta. See [Enable the remote MCP server](/integrate/mcp#enable-the-remote-mcp-server) for setup steps. ## April 9, 2026 > Review Unleash v7.6.0 release notes, including project-level context fields and editable activation strategies in applied release plans. # Unleash v7.6.0 ## Project-level context fields [Context fields](/concepts/unleash-context) 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](/concepts/activation-strategies) and the [playground](/concepts/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](/concepts/activation-strategies) in a [release plan](/concepts/release-templates) after the release template is applied to a feature flag. You can edit the configuration, [constraints](/concepts/activation-strategies#constraints), [variants](/concepts/strategy-variants), [rollout percentage](/concepts/activation-strategies#rollout-percentage), or set the status to **Inactive**, just as you would with any standalone strategy. ## March 4, 2026 > Review Unleash v7.5.0 release notes, including project group access updates, Edge API URLs, private project scoping fixes, and MCP beta. # Unleash v7.5.0 ## User groups with root roles can now be assigned to projects Previously, [groups](/concepts/rbac#user-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](/concepts/sso), 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](/unleash-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](/concepts/project-collaboration-mode#private-collaboration-mode) 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](/concepts/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](/concepts/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](mailto:beta@getunleash.io). We've also launched the [Unleash MCP server](/integrate/mcp) 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. ## December 12, 2025 > Review Unleash v7.4.0 release notes, including Enterprise Edge observability, Edge OSS maintenance dates, and global change request overview. # Unleash v7.4.0 ## Enterprise Edge observability We extended the observability dashboard for [Unleash Enterprise Edge](/unleash-edge). The dashboard provides visibility into the health and performance of your hosted or self-hosted Enterprise Edge nodes directly within the Unleash Admin UI. Key metrics include: * **Instance details**: Region, instance ID, upstream server, and hosting type. * **Health resources**: Current connection status, running version, and real-time CPU and memory usage. * **Traffic and performance**: Active streaming clients and granular latency breakdowns for upstream syncs (features, metrics) and downstream evaluations. ### Announcement: Unleash Edge OSS enters long-term maintenance We are sunsetting the Open Source Software (OSS) version of Unleash Edge to focus on Enterprise Edge capabilities. The lifecycle for the OSS version is as follows: * **Long-term support**: starts December 12, 2025 * **End-of-life**: December 31, 2026 We recommend that all OSS users of Edge migrate to [Enterprise Edge](/unleash-edge#how-to-get-enterprise-edge) to ensure continued support and access to security updates. ### Global change request overview We added a global overview for [change requests](/concepts/change-requests). The table allows you to view all your open and closed change requests in a single location. You can filter the table to show: * **Created by me**: Change requests created by you. * **Approval requested**: Change requests requesting your approval. ## November 7, 2025 > Review Unleash v7.3.0 release notes, including strategy setup improvements, new lifecycle analytics, and aligned Project Overview filters. # Unleash v7.3.0 ## Improved experience for adding strategies to flags We redesigned how you add [activation strategies](/concepts/activation-strategies) to flags. The new flow makes it easier to access standard strategies and reusable [release templates](/concepts/release-templates). When you configure a flag in an environment, click Add strategy and choose one of the following options: * The [project's default strategy](/concepts/activation-strategies#default-strategy) * A [standard strategy](/concepts/activation-strategies#standard-strategies), such as gradual rollout or on/off * An [advanced strategy](/concepts/activation-strategies#advanced-strategies), such as IP or host targeting * A [release template](/concepts/release-templates) * A [custom activation strategy](/concepts/custom-activation-strategies) defined in your instance You'll also see a suggested strategy in any environment without an active configuration, so you can preview, edit, or apply your default strategy in a single click. ### New lifecycle analytics We've added two new widgets to the [Analytics](/concepts/insights) dashboard: **New flags in production** and **Flags archived vs flags created**. **New flags in production** shows how many flags reached production each week for your selected time period. It gives you a quick view of your team's delivery pace and how feature output changes over time. **Flags archived vs. created track**s how many flags you archive each week compared to how many you create, alongside your average cleanup ratio. If you consistently create more flags than you archive, that's a sign that technical debt may be increasing. Over time, aim for a 1:1 ratio (or 100%) of archived to created flags to keep your codebase healthy. ### Aligned quick filters in Project Overview We aligned quick filters in **Project Overview** to provide a more consistent experience with feature flags lists. You can now use the same filters available on **Flags Overview** to narrow down flags by [lifecycle stage](/concepts/feature-flags#lifecycle-stages), such as *Develop*, *Production*, or *Clean-up*. ## September 3, 2025 > Review Unleash v7.2.0 release notes, including Release Management, change request updates, lifecycle metrics, safe archiving, and unknown flag checks. # Unleash v7.2.0 ## Release Management We've launched **Release Management** to help you standardize how you roll out new features. You can now define reusable [release templates](/concepts/release-templates) with milestones so you don't have to manually configure the same rollout strategies across multiple flags. This reduces repetitive work, ensures consistent rollouts, and lowers release risk. Create new templates under **Configure > Release templates**. ## Change request improvements You now receive an email notification when you're added as a reviewer to a [change request](/concepts/change-requests). This helps you maintain momentum by speeding up the approval process. Change requests also display a cleaner, formatted JSON diff that highlights only the changed values while still letting you expand for the full object. In the new **View diff** tab, you can review the changes in detail, and easily copy them without relying on tooltips. In addition, to give you a clear timeline of progress, every state update to a change request now includes a timestamp. ## Flag performance and lifecycle updates We've added [lifecycle metrics](/concepts/insights) to the **Analytics** dashboard so you can see a snapshot of how many flags are currently in each major lifecycle stage: Develop, Production, and Cleanup. Each stage shows how many flags are new this week, how many have been there for more than a week, and the median time flags spend in that stage. You can also compare this to the historical median to spot outliers. This gives you a clear picture of where flags may be stuck, helps you reduce technical debt, and connects engineering work to business outcomes. To help reduce technical debt, Unleash now also suggests flags that are [safe to archive](/concepts/feature-flags#archive-a-feature-flag). By analyzing usage, the platform highlights flags in the cleanup stage that haven't been used for seven days so you can confidently archive them in bulk. ## Project list improvements The **Project list** view has been redesigned to make it easier to scan, even with a large number of projects. You can now switch between card and list views depending on which format you prefer, making navigation more flexible. ## Unknown flag checker Unleash now highlights any flags your SDKs try to evaluate that Unleash doesn’t recognize. You’ll see these in the **Flags overview** under **Unknown flags**, where you can review the full list to spot typos, fix misconfigurations, or remove stale references in your code. This helps keep your setup clean and in sync. ## August 13, 2025 > Review Unleash v7.1.0 release notes, including lifecycle cleanup updates, technical debt insights, SDK naming changes, and grouped Event Log events. # 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](/concepts/technical-debt) 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](/sdks) and [API tokens](/concepts/api-tokens-and-client-keys). Server-side SDKs are now **backend SDK**s, 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](/concepts/events#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](/concepts/change-requests) 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](/api/search-events). ### View connected frontend applications To help debug [frontend application connections](/concepts/applications), 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. ## June 11, 2025 > Review Unleash v7.0.0 release notes, including flag cleanup reminders, external links, tag colors, improved flag search, and API removals. # Unleash v7.0.0 ## Flag cleanup reminders and automation To help you stay on top of technical debt, we've introduced automated reminders for flag cleanup. When a feature flag reaches its intended cleanup date and we no longer detect metrics, we’ll remind you to change its lifecycle status to **Cleanup**. This highlights the flag in the UI, making it clear which flags are ready to be removed. On the flag's page, you will see a reminder to remove the flag from your codebase and archive it in Unleash. ## External links on feature flags You can now add external links to your feature flags, allowing you to connect directly to related resources like key metrics, analytics, or issue trackers. Add a link on the **Overview** page of any feature flag. In addition, you can define link templates at the project level in **Settings > Project settings > Enterprise settings > Project link templates**. These templates automatically populate links for all new feature flags within that project. For example, you can create templates to find all usages of a feature flag in your repository or automatically link to a Jira issue when a flag is created from Jira ## Colors on tags To help you visually differentiate and organize your feature flags, you can now add colors to [tags](/concepts/feature-flags#tags). When you create or edit a tag in **Configure > Tag types**, you can assign a specific color. This makes it easier to quickly identify and manage flags, especially in projects with many tags. ## Improved flag search and Admin UI menu We've renamed **Search** to **Flags overview**, to create a centralized place to monitor the status and lifecycle of all your feature flags and releases. This is particularly useful for coordinating flags across multiple teams. With **Flags overview**, you can get a clear picture of where each flag is in its lifecycle and its current status—replacing the need for manual tracking or spreadsheets. We've also redesigned the **Configure** menu and removed redundant items such as **Recent projects** and **Recent flags**, which are now accessible from the main **Dashboard**. ## Simplified activation strategies and constraints We simplified the process of adding or editing [activation strategies](/concepts/activation-strategies) and constraints. Use **Add strategy** to add the default activation strategy to a flag; use **More strategies** to select a different strategy type or get an overview of all available release templates. ## Removed deprecated endpoints and schema properties As part of our commitment to maintaining a clean and robust codebase, several deprecated API endpoints and schema properties have been removed in Unleash v7. Refer to our [Migration guide](/deploy/upgrading-unleash) for a detailed list of API changes and additional help with upgrading to Unleash 7. ## April 2, 2025 > Review Unleash v6.7.0 release notes, including Access overview, Event Log IP addresses, optional project owners, and new root permissions. # Unleash v6.7.0 ## Improved user roles and permissions overview We've added a new **Access overview** page for each user, making it easier for administrators to see exactly what a user can do in Unleash and which roles grant those permissions. You can explore permissions at the root level or for specific environments and projects. To view a user's permissions, go to **Admin settings > Users**. Select a user and click **Access overview**. ## IP addresses in Event Log The [Event Log](/concepts/events#event-log) now records the IP address of the user who performed each action. This feature requires an Unleash Enterprise plan. ## Projects no longer require an Owner We removed the requirement for projects to have an [Owner](/concepts/rbac#predefined-roles). This gives you full flexibility when it comes to customizing the project-level roles. Projects without an Owner are shown as owned by System. ## New root-level permissions for authentication and instance maintenance We've introduced five new [root-level permissions](/concepts/rbac#root-permissions) to give more granular control over features that were previously restricted to the Admin role. These permissions cover authentication settings such as single sign-on, instance maintenance tasks like updating banners and toggling maintenance mode, managing CORS settings, and viewing access logs and login history. ## March 6, 2025 > Review Unleash v6.6.0 release notes, including Edge observability metrics, data usage date ranges, and Event Timeline dashboard updates. # Unleash v6.6.0 ## Observability metrics for Edge We've introduced a [new dashboard](/concepts/network-view#connected-edges) that provides detailed observability metrics for Unleash Edge, helping teams efficiently manage all their connected Edge instances. The dashboard offers a high-level view of all Edge instances, with deeper insights into instance ID, region, CPU and memory usage, and upstream/downstream latency. This data helps you ensure that all instances are operational and quickly identify potential issues. You can access these metrics in **Network > Connected Edges** for Edge instances on version 19.7.0 or later. ## Data usage date range selector The Data Usage dashboard now provides an aggregated view of your requests to Unleash over the last 3, 6, or 12 months—making it simple to track and assess your data usage over time. You can also compare your usage in previous months with the current month. Access the dashboard in **Network > Data Usage**. ## Event Timeline now lives in Dashboard We have moved **Event Timeline** to the top of **Dashboard** for a more seamless experience and easier access. ## February 11, 2025 > Review Unleash v6.5.0 release notes, including renamed feature flag lifecycle stages and updated license policy details for self-hosted Enterprise. # Unleash v6.5.0 ## Renamed feature flag lifecycle stages We've updated the names of the [feature flag lifecycle](/concepts/feature-flags#feature-flag-lifecycle) stages to better mirror a typical software development process and help you improve your release efficiency and workflows. The changes include updates to the names, icons, and colors for the different stages. ## Updated license policy for self-hosted Enterprise Since Unleash v6.0, we've had soft limits in place warning self-hosted Enterprise instances operating without a [valid license](/deploy/license-keys) or exceeding their seat count. With Unleash v6.7, we have introduced the following restrictions: ### Mandatory license for enterprise self-hosted plan If you don't have a valid license, your Unleash instance enters read-only mode, and the only available action is to install a valid license. ### License expiration When your license expires, your Unleash instance enters read-only mode. The only available action is to install a new, valid license. Connected applications continue to operate and receive current feature flags, but users cannot make any changes to Unleash. ### Seat count If you reach the maximum number of seats in your license, you cannot add new users until you remove existing users to stay within your limit. The Unleash Admin UI displays warning banners for customers approaching or exceeding the terms of their license. ## January 14, 2025 # Unleash v6.4.0 ## Simplified projects We've simplified the experience of managing your projects in Unleash. On the project overview page, you can now use filters to access [archived](/concepts/feature-flags#view-archived-flags) or [stale](/concepts/feature-flags#view-archived-flags) flags. Additional enhancements, such as tooltips and accessibility improvements, provide a more consistent and focused experience. ## Project status dashboard We've introduced a new [Project status dashboard](/concepts/technical-debt#project-status) to help you monitor your projects more effectively. The dashboard provides an overview of: * Project health * Project resources: members, API keys, and segments * Project activity * Flag lifecycle data ## Deprecated Admin tokens We've deprecated Admin tokens to encourage using more secure and granular access to resources. You can use [personal access tokens](/concepts/api-tokens-and-client-keys#personal-access-tokens) or [service accounts](/concepts/service-accounts) instead. ## Restrictions on account sharing We've implemented security measures to detect shared accounts as they impede the ability to trace and audit changes. You can find further recommendations and best practices on our [blog](https://www.getunleash.io/blog/stop-sharing-accounts).