v0.18.1

Engine

Omaweb now depends on omaweb-qtwebengine>=6.11.3-1, so upgrading brings QtWebEngine 6.11.3 with it. That engine is Chromium 140.0.7339.264 and includes Chromium's security fixes up to 155.0.8059.85. QtWebEngine 6.11.2 included them only up to 151.0.7922.71. The Engine security baseline now names 6.11.3, and Settings reports a build on 6.11.2 as below it.

Private windows from the command line

omaweb --incognito and omaweb --private-window open a Private window, with the launch address in it when you give one. Omarchy's private browser key, Super+Shift+Alt+B, passes --incognito, so it now opens a Private window instead of an ordinary one.

When Omaweb is already running, the request goes to the running browser. If a Private window is open, Omaweb reuses the one shown most recently. The address opens as a new tab there, and with no address the window comes forward. A session with no Private windows available, such as one launched with a debugging listener, opens nothing instead of putting the page in the main window's history. omaweb help lists both switches.

Fixes

• The Sync avatar in the sidebar footer draws as a circle. Before, the photo kept its square corners.
• Updating the Omarchy kit made a prompt's Allow and Deny buttons lie over one another, so a click on Allow reached Deny. The buttons now size to their labels.

Full changelog: https://github.com/villekivela/omaweb/compare/v0.18.0...v0.18.1