Newsletter: What's new in Unleash v8.3
Hi there!
Unleash 8.3 is out. Adding strategies to a flag got a lot simpler and new constraint operators help with precise targeting. We also have new OpenFeature providers, four conferences in November, and a hands-on workshop at W-JAX. Let's get into it.
What's new in Unleash 8.3
Secure token storage
Every backend, frontend, personal access, and service account token you create in 8.3 or later is a secure token. Unleash stores a hash instead of the token, so nothing in the database or its backups can be turned back into a working credential. Tokens created before 8.3 keep working, but their complete values stay in the database until you delete them, so rotate them when you can. We explain the reasoning, what the change does and doesn't protect, and how to rotate in Why we're doubling down on API token security.
Simplified Add strategy dialog
We simplified the flow of adding strategies to a flag: use the project default, set up a gradual rollout manually, or start from a release template.
Regex, IP address, and SemVer constraint operators
The regex operator matches a context field against a regular expression, with a tester in the Admin UI. The IP address operator checks whether a field falls within a list of IPv4 or IPv6 addresses or CIDR ranges. And the SemVer operators now include greater-than-or-equal and less-than-or-equal.
And more...
You can now delete tags you no longer need, flag links have moved into the Flag details panel, and the Unleash MCP server can send anonymous feedback reports when a tool call fails, so we can prioritize fixes.
Use Unleash through OpenFeature
If your organization standardizes on OpenFeature, the CNCF's vendor-neutral feature flag API, you can now evaluate Unleash flags through it with providers we maintain for Node.js, PHP, Python, Ruby, Rust, Swift, and Android. Each provider wraps the Unleash SDK for that language, so you keep local evaluation, caching, and usage metrics, while your application code depends only on the OpenFeature API. Community providers cover Go, Java, .NET, and browser JavaScript.
It's also the fastest way to switch from another feature flag system: if your code already calls OpenFeature, moving to Unleash is a provider swap, with no changes at the evaluation call sites. The new docs cover setup for each language, how OpenFeature context maps to Unleash context, and what the providers don't support compared with the Unleash SDKs.
Meet us in November
The Unleash team is on the road all month. Come say hello at an event, or email us and we'll find time for a coffee.
W-JAX Munich, 3 to 5 November. We're running a hands-on workshop, FeatureOps: From First Flag to Runtime Control. Bring a laptop: you'll create your first flag, wrap a change behind it, roll it out progressively, and finish with the runtime controls that let you turn a feature off in seconds without a redeploy. Kickoff is at 16:45 CET on 4 Nov. Seats are limited, so register early if you're attending the conference.
- W-JAX Munich, 3 to 5 November (meet us there)
- Open Source in Finance Forum, New York, 4 to 5 November (meet us there)
- QCon San Francisco, 16 to 18 November (meet us there)
- AWS re:Invent, Las Vegas, 30 November to 4 December (meet us there)
We build Unleash together with users like you. Let us know if you want to be included when we discover new ideas and ways to make our product better.
We typically send out a newsletter monthly with our new releases to share useful and interesting updates.
Bricks Software AS, Edvard Storms gate 2, Oslo, Norway 0166