omaforge 0.2.8: fixes from a full QA pass

omaforge is the World of Warcraft addon manager for Linux and Omarchy. Version 0.2.8 is a fixes release from a full QA pass, coming the same day as 0.2.7.

What’s fixed

Safer uninstall. omaforge uninstall now asks before removing an addon it can’t trace to a source, such as one you wrote yourself. Without a terminal it refuses unless you pass --yes.

Damaged files no longer crash omaforge or lose data. A broken config.toml or flavors.toml gives a one-line message naming the file and the problem, and omaforge never writes over it. In the app, a red banner names the file and offers Open file, Rescan, or setting it aside (it’s kept as <name>.broken-<time>). A damaged state.json is moved to state.json.damaged-<time> and a fresh one is started, with a warning in both the CLI and the app.

Fits half a screen. The window now goes down to 640 px wide. Below 1000 px the sidebar narrows, the tabs move under the title, and less-used actions (Import/Export, and each addon’s channel, Pin, Ignore and Remove) move into a ⋯ menu. Alt+↑ and Alt+↓ switch between game versions.

Clearer messages. An unknown addon id, an AddOns folder omaforge can’t write to, an unknown root or provider, and an empty GitHub search now say what went wrong in plain words. CurseForge versions no longer show up as 1.0.1.zip or offer an update that isn’t there, check lists each addon it couldn’t check and why, and Wago says plainly that it isn’t supported yet.

Get it

• Arch / Omarchy: sudo pacman -U omaforge-0.2.8-1-any.pkg.tar.zst, then omaforge setup omarchy
• Debian 13+ / Ubuntu 26.04+: sudo apt install ./omaforge_0.2.8-1_all.deb
• Fedora: sudo dnf install ./omaforge-0.2.8-1.noarch.rpm
• Any other Linux: the AppImage, chmod +x omaforge-0.2.8-x86_64.AppImage && ./omaforge-0.2.8-x86_64.AppImage. Add --install-desktop-entry to put it in your app menu.
• With autonomix-cli: autonomix-cli add https://github.com/ninepointlabs/omaforge

The packages are on the v0.2.8 release, and the source is on GitHub.