How can I update Omarchy without updating optional AUR applications

[ammarove]

When I run omarchy update, it also runs the AUR update step and upgrades all my user-installed applications. For example, the latest update attempted to upgrade Android Studio, DataGrip, IntelliJ IDEA, Brave, Slack, Postman, OpenCode, and several other large applications.
I want to update Omarchy and the required Arch system packages, while leaving optional applications at their current versions so I can update them separately.
Is there a supported way to:

• Skip optional AUR applications during the Omarchy update, or
• Select which AUR applications should be updated?
  I understand that partial Arch system upgrades are unsupported. I am only asking about explicitly installed optional AUR applications, not core libraries or packages required by Omarchy.
  Could omarchy update provide a “skip optional AUR apps” option or an application-selection screen?
  For the prompt in your example, entering 1-17 excludes all 17 AUR updates for that run. However, a built-in Omarchy option would be clearer and safer. Do not use omarchy update -y, because that removes the opportunity to exclude packages.

[ChangkeunJ]

There's a supported way to get this today without omarchy growing an option for it, and it survives omarchy updates, which matters because editing the scripts yourself wouldn't.

The AUR step is one line:

yay -Sua --noconfirm --cleanafter --ignore gcc14,gcc14-libs

So it's yay, and yay honours IgnorePkg out of /etc/pacman.conf. Put your applications in there:

IgnorePkg = android-studio datagrip intellij-idea-ultimate-edition brave-bin slack-desktop postman-bin opencode-bin

and from then on every omarchy update leaves them alone, with no prompt to catch and no exclusion list to retype each run. omarchy is already leaning on the same mechanism for gcc14, just through the flag rather than the config file.

When you do want one of them moved, name it explicitly:

yay -S android-studio

pacman spots that it's in IgnorePkg, asks once whether you really meant it, and carries on. Which is the update-them-separately workflow you were after.

One thing worth checking at your end. That AUR command carries --noconfirm, so the AUR step shouldn't be stopping to ask anything at all. The numbered prompt you're answering 1-17 at is more likely the system package step earlier in the run, in which case it isn't excluding what you think it's excluding. Easy enough to confirm from /tmp/omarchy-update.log, since the whole run gets captured there.

On the risk, since you raised it yourself: holding these back is a far smaller thing than a partial system upgrade. They're leaf applications and nothing links against them. The failure you can still hit is one of them breaking after a soname bump in something it does link to, icu and openssl being the usual suspects, and the fix there is to rebuild it, which for an AUR package is what an update does anyway.