> Markdown version of https://www.getunleash.io//blog/unleash-7-3
> For clean Markdown of any blog post, append .md to its URL.
> For a site index, see https://www.getunleash.io//llms.txt.

# Unleash 7.3

_Published 2025-11-07 by Melinda Fekete in Product._

We’re excited to share that Unleash 7.3 is out!

In this release, we’ve redesigned how you add [activation strategies](https://docs.getunleash.io/reference/activation-strategies) to feature flags. The new flow makes it easier to access standard strategies like gradual rollouts, advanced targeting, and your powerful, reusable [release templates](https://docs.getunleash.io/reference/release-templates), in a single, simplified menu.

**Why it matters**:

-   **Faster config**: Get to the right strategy in fewer clicks.
-   **Better access to release templates**: Standardize your rollouts by applying release templates directly.
-   **Smarter suggestions**: Environments without an active configuration now suggest your project’s default strategy, letting you preview, edit, or apply it in a single click.

You’ll also notice that Project Overview feels more consistent. We’ve aligned quick filters across the board, so your feature flag views match the main list and make it easier to track the full [lifecycle](https://www.getunleash.io/blog/feature-lifecycle-management), from Develop to Clean-up.

And 7.3 introduces new [lifecycle analytic](https://docs.getunleash.io/reference/insights)s to help you understand your team’s feature flag health and delivery pace. The new widgets show how many flags ship each week and how well you’re keeping up with cleanup, giving you a clear view of delivery velocity and long-term technical debt.

[Read the full 7.3 release notes](https://github.com/Unleash/unleash/releases/tag/v7.3.0)

## When us-east-1 went sideways (and we were right there with you)

If you were caught in the recent AWS outage, you weren’t alone. We know how stressful and disruptive those incidents can be.

Unleash services stayed [fully operational](https://unleash.instatus.com) throughout the incident. Our infrastructure is designed for high availability, and our pre-provisioned capacity ensured uninterrupted service for all customers. While we temporarily paused our deployments, all running workloads and databases continued to operate normally.

![](https://cdn.getunleash.io/uploads/2025/11/Screenshot-2025-11-05-at-20.32.13-1024x733.png)

Moments like this are humbling reminders that **resilience is an ongoing practice**, not a checkbox. We’ve used this event as an opportunity to review and strengthen our own dependency strategies to stay even sturdier next time.

Want to learn more about how Unleash scales and how we architect for resilience? [Read our architecture scaling guide](https://docs.getunleash.io/feature-flag-tutorials/use-cases/scaling-unleash).

## Hello from PlatformCon Paris

We were recently at **PlatformCon Paris**, where [Kelsey Hightower](https://en.wikipedia.org/wiki/Kelsey_Hightower) reminded everyone that you’ve got to scale down before you can scale up. It was a grounded keynote about the evolution of platform engineering,  and a good reminder that as AI changes how we build, strong fundamentals still matter most.

The best teams we met aren’t skipping the basics like CI/CD or feature flags, they’re doubling down on them.

![](https://cdn.getunleash.io/uploads/2025/11/ARIANE_STANDS_UNLEASH-5-1024x683.jpg)

As we plan for 2026, [let us know](https://www.getunleash.io/unleash-community) which events you’ll be at and where you’d like to meet the Unleash team!