MangoWM 0.18.3 ships a focused patch release, no new features
MangoWM, the Wayland compositor that bills itself as "dwm but Wayland," has published 0.18.3. It's the smallest possible update: no new features, no breaking changes, just a handful of fixes and small optimizations.
This is a compositor that positions itself right where dwl ends. It keeps dwl's lean, fast-build C philosophy and stacks on the features that make a compositor usable day to day without taking on the weight of something like Sway. Think per-tag layouts, smooth animations, blur and shadow effects, an IPC client, and hot-reloadable config. As of right now it has close to 3,900 stars and ships under GPL-3.0.
Maintainer DreamMaoMao pushed the tag today. The changelog lists two optimizations and three bug fixes. But between the previous tag, 0.18.2, and this one there were 17 commits across 23 files by four contributors. Not that the terse notes tell you that.
The changes in 0.18.3
The optimizations are small. One stops window-close and layer animations from spilling onto your other monitors. If you run multiple displays, you'll want that. The other keeps blur active on fullscreen windows that use an alpha channel, since those had lost their effect when maximized.
Neither of these will set the internet on fire. But they're exactly the kind of polish that separates "it works" from "it feels right."
The three fixes are where the more careful work sits. The scratchpad ratio fix restores expected sizing for named scratchpad windows, a config knob that had been silently ignoring you. The drag-and-drop lag fix helps when you've got global VRR enabled. A stuttering drag is something you stop noticing the moment it's gone.
Then the one that drew the most care: community contributor intiluha patched a case where a layer surface mapping under a still pointer never received an enter event. In plain terms, slurp would reveal its crosshair only after you moved the mouse. The commit message is unusually thorough for a Wayland fix, walking through why the map listener must register after wlr_scene_layer_surface_v1_create. That sort of detail tells you someone actually read the wlroots source.
Build, context, and what's next
Mango is still a from-source project in practice. There are no prebuilt binaries or AppImage attached to this release, just source tarballs. Keep in mind that you'll still need to build wlroots 0.20 and scenefx 0.5 by hand before mango will even compile, then run meson and ninja. Distributions like Arch, Fedora, Gentoo, Void, and Guix ship packages for it, though Void calls its package mangowc, which always catches people out.
The release cadence here is relentless. 0.18.0 landed on October 9th as a major release, with breaking config renames and a migration script. 0.18.2 followed just six days later, on the 18th. This one simply fills in the cracks between milestones, fitting the project's stated stability-first stance.
There's also a contribution policy worth flagging. Direct AI-generated PRs aren't accepted. Contributors must understand the code they submit, and you can only use AI to draft a bug report. Given how thoroughly intiluha's patch reads, the rule seems to be holding up.
It's a textbook patch release. Not every update needs a headline feature, and 0.18.3 does exactly what it says it will.
Head here to the release page for the full changelog.
