Hyprland 0.55.1 Rolls Out with Fixes for Lua Configs and Rendering

Hyprland 0.55.1 has been released as the first maintenance update after the major Hyprland 0.55 release. As previously reported, Hyprland 0.55 introduced support for Lua-based configuration files while continuing to support the older Hyprlang format.

This new update focuses heavily on Lua-related improvements. Hyprland 0.55.1 adds fixes that allow monitors to be re-enabled through Lua configurations, limits package module loading to Lua-only modules, and updates Lua permission stubs. It also resolves issues with plugin variables containing dashes, which impacted some third-party plugin setups.

For monitor management, the release fixes cursor bounds not refreshing correctly after monitor layout changes, prevents unnecessary modesets when only reserved regions are modified, and stops displays from reverting to 8-bit color depth when monitor rules are applied. It also corrects top-layer bar visibility issues when switching workspaces while using scrolling layout fullscreen mode.

The update further introduces several rendering fixes, including corrections for shader premultiplication, framebuffer swizzle comparisons, and snapshot image descriptions. These low-level improvements are aimed at enhancing rendering accuracy and display behavior rather than introducing new user-facing features.

Additionally, Hyprland 0.55.1 improves synchronization between a window’s monitor and workspace when grouped, prevents pinned window states from changing during workspace transitions, and properly marks input-blocked windows as inaccessible. It also resolves an invalid capture issue in vectorToWindowUnified.

The release includes multiple crash fixes as well. The config property refresher no longer crashes when the event loop manager is unavailable, while the scroll_move gesture path now contains an additional safeguard to prevent crashes. Smaller maintenance updates are also included, such as adding a missing numbers header and fixing legacy configuration logging behavior.

For more details, see the changelog.