How Omarchy Updates Work: Stable, RC, Edge and Dev Channels

Omarchy is based on Arch Linux, but its supported update process is not simply "run pacman -Syu whenever you feel like it."

An Omarchy update coordinates several things together:

• Omarchy packages;
• Arch packages;
• AUR packages when present;
• configuration updates;
• migrations;
• a pre-update system snapshot.

The supported path is Update > Omarchy from the Omarchy menu or the omarchy update command.

The four channels

Omarchy currently provides four update channels.

Channel	Purpose
stable	Default channel for ordinary users
RC	Final validation before a major release
edge	Newer development builds and current Arch packages
dev	Source checkout plus edge packages for contributors

The right choice is about how much breakage and recovery work you are willing to tolerate, not about winning a race for the newest package.

Stable

New installations start on stable.

Stable tracks official Omarchy releases.

The current manual says its Omarchy Arch mirror intentionally runs about one month behind the newest Arch packages so incompatibilities that require configuration changes can be identified before reaching ordinary users.

That delay is deliberate.

RC

The RC, or release-candidate, channel is used for final testing before a major Omarchy release.

It is useful for people who specifically want to help validate an upcoming release.

It is not simply "stable but faster."

The point is to expose the release candidate to additional real-world testing.

Edge

Edge tracks current Omarchy development builds and newer Arch packages.

The official manual says edge is for experienced Linux users who know how to recover a system when something goes wrong.

If the only reason you want edge is "newer must be better," stable is probably the better fit.

Dev

The dev channel links Omarchy directly to a Git checkout at:

~/omarchy

and combines that source tree with edge packages.

That is aimed at contributors and experienced users actively working on Omarchy itself.

It carries the highest expectation that the user can tolerate and diagnose breakage.

Switching channels

The current supported methods are:

• Update > Channel in the Omarchy menu;
• omarchy-channel-set in the terminal.

Changing channels changes what update stream the system follows.

Do not switch casually without understanding how package versions may move forward or backward when changing streams.

Why direct pacman/yay system upgrades are different

A stock Arch habit is to run:

pacman -Syu

or an AUR-helper equivalent.

Omarchy warns against using those commands for ordinary system upgrades because they bypass the coordinated Omarchy workflow.

The current system actually intercepts a direct system upgrade and points the user to omarchy update.

That protects the pieces Omarchy needs to move together: packages, migrations, configuration updates and snapshots.

A snapshot is taken before updating

Omarchy's update flow creates a system snapshot before the update.

If an update causes problems, the manual says you can reboot and choose the pre-update snapshot from the bootloader.

That gives you a recovery option.

It is not a substitute for backups of important personal data.

A snapshot can help restore system state; it should not be treated as the only copy of irreplaceable files.

Reinstall is a stronger reset

The command:

omarchy reinstall

can reinstall default Omarchy packages and configuration and return the system to stable.

The manual warns that this can overwrite user changes made to Omarchy default configuration files.

That is one reason to keep personal configuration in the intended user-owned locations.

For the broader system model, see What Is Omarchy?.

The practical rule is simple: use Omarchy's update path unless you intentionally know why you are bypassing it.