Bottles 67.5 ships Eagle tracing and a login bridge in one of its most substantial patches yet
The maintainer pushed 176 commits on October 27th, extending the project's Eagle analysis tool and a new credential bridge to its Soda runners.
Bottles 67.5 went live on October 27th with 176 commits and 135 files changed. That's close to one of the most code-heavy single patches the open-source runner has shipped in recent memory. It also arrived the way Bottles almost always does: through Mirko Brombin, who maintains the project under the handle "~ Mirko."
What 67.5 actually adds
The two headline changes both live in the "Added" section, and both target the Soda runner family specifically.
First is optional Eagle tracing alongside native analysis for compatible Soda runners. Eagle is Bottles' pre-launch analyzer. It inspects a Windows executable before you run it, using YARA pattern matching and pefile to predict what might break and how to fix it. 67.5 adds a tracing pass so Eagle can pinpoint issues at a finer granularity when Soda is in play. Other runners keep their existing path, so nothing gets disrupted for the broader user base.
The second, and frankly more interesting one, is an identity bridge for those same runners. Picture browser-based logins: the OAuth-style flow where Epic Games, Discord, or a Microsoft account hands you back a session after you authenticate in a browser. This bridge catches that return flow and stores the credentials in your desktop's system keyring, like GNOME Keyring, instead of leaving tokens lying around in plaintext.
There's a smaller touch too. Playtime totals now display in hours rather than whatever finer-grained units they used before.
What's actually being fixed
The bulk of 67.5 is fixes, and it spans a wide area.
Keep in mind that several of these hit real pain points. Offline component downloads work again, including the fallback catalog correctly handling software you already have installed. Dependency installers that were invoked with Z: disabled now behave, font installs report failures properly, and broken installers actually tell you when they broke.
Bottle restoration got attention as well. Importing a bottle's prefix architecture was fixed, and user files are now preserved when you restore a bottle on a different account. If you've ever rebuilt a machine or moved between accounts, you understand how much that matters.
Library tweaks fix desktop shortcuts, drag-and-drop, bottle ordering, and component-removal controls. UMU games got controller access and failed game-search retries sorted. The Wayland setting for Proton launches was corrected too.
A few of these fixes nod to a security thread that's been building since 67.2, which closed a hole exposing your host root to UMU sandboxes. Moving credential handling into the system keyring fits that same instinct. A Wine manager able to run installers and juggle accounts is a large attack surface, and avoiding cleartext token storage sidesteps a fair amount of risk. For context, the project's last notable vulnerability was CVE-2023-22970 in 2023, a YAML loading bug that allowed remote code execution through a crafted file and was fixed back in 51.0.
The 67.x sprint and what's next
If you've been following Bottles, 67.5 will look familiar in shape. It's the tail of an unusually fast release streak running late August through late October 2026, during which releases came almost daily, then every few days.
The recent run reads like a work order. 67.0 on August 31st enabled Adaptive Launch for ProtoSoda and killed a Wine race-condition crash. 67.1 a week later was a hotfix that repaired the UMU runtime after a sandbox regression broke game launches. 67.2 closed that host-root security hole. 67.3 and 67.4 pushed fixes to the Soda 11.0-10 runner. Then 67.5 lands here with the Eagle and identity-bridge work on top.
The throughline is easy to spot: over these weeks the project has been hardening its Soda, UMU, Eagle, and Adaptive Launch stack while tightening sandbox security and polishing the Library. Adaptive Launch alone is worth a mention — a learning feature that watches which files a program touches on startup and pre-prepares them on later launches. Bottles claims the median cold-start time improved by roughly 3.38 percent, with major page faults dropping from 16 down to 1. The profile stores file paths only, never file contents, and uploads nothing.
All of this lands in the current Bottles today. The from-scratch Rust rewrite, Bottles Next, is what Brombin calls "genuinely around the corner, although that does not mean tomorrow." Built on the project's own next-ui toolkit over Iced, Next will eventually inherit the Eagle tracing and identity bridge along with everything else. Brombin has been clear the current app will keep support through its anniversary, since it still has people to serve.
For what it's worth, this all runs mostly on public money. Bottles got a grant from NLnet's NGI0 Commons Fund starting in August 2025, aimed at speeding up Next. Brombin has been upfront the grant doesn't make the project financially secure, which keeps community donations important. It's about as much as one maintainer can carry.
Head here to grab it from Flathub. An experimental cpak package is also available. You find the source code here.
