> 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.

> 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.