Bottles 66.6 drops six hotfixes in under 28 hours to stabilize the 66 release train
Bottles 66.0 shipped on August 11, 2026. If you've been holding off on updating until the dust settled, you can update now. The development team, led by maintainer mirkoBrombin, pushed five additional hotfixes in the following 27 hours. Version 66.6 is live on Flathub. Not bad for a sprint.
The 66 release brought some heavy features to the Linux compatibility layer. Keep in mind that the new version integrates the UMU launcher for Steam and Proton titles, uses ProtoSoda as the default runtime, and adds adaptive launch logic. It also introduces an experimental cpak package format. The release notes mention official runner logos, cover picker improvements, and various fixes to dependency actions. The math checks out, too. From the first commit of 66.0 to the final commit of 66.6, the team spent exactly 27 hours and 28 minutes pushing code.
The hotfix cascade
The stack of fixes that followed tells a familiar story for open-source maintainers. Major releases expose edge cases. The team responded by shipping a cascade of hotfixes between August 12 and August 14.
Bottles 66.1 arrived just 12 hours after the major release. It targeted two specific UI issues: Flatpak-based Wine runners were vanishing from the interface, and the file chooser for custom UMU prefixes wasn't responding to input.
Bottles 66.2 hit the next day. This was the largest hotfix of the cycle. It fixed the Steam runtime failing to pass dash arguments, replaced case-insensitive DLL duplicates, and improved NVK detection inside Flatpak. It also handled mixed library entries and moved network requests off the UI thread to stop interface freezes during background operations.
The fixes kept coming. Bottles 66.3 stopped external executables from incorrectly receiving a Z drive mapping. Bottles 66.4 preserved case-normalized dependency DLLs. Bottles 66.5 made dependencies selectable directly from list rows and clarified Proton runtime guidance. Bottles 66.6, the final push, ensures the sandbox stops before you delete a bottle.
What this means
The rapid cadence attracted new contributors. @alairon and @bunlongheng made their first contributions during this cycle. However, at the same time, the intense focus on hotfixes means the user experience might feel slightly disjointed for those tracking individual changelogs. GitHub reactions showed 66.0 pulled 12 reactions, while 66.2 drew 8 reactions. mirkoBrombin handled the bulk of the code changes, while the new contributors landed their first pull requests in the final days of the window.
The release is available via Flathub and the new official cpak channel.
