[ryanrhughes]

Automated update of a package that tracks an upstream vendor release
feed or branch tip rather than the AUR.

Release watches and providers are declared in .omarchy/package.json;
exceptional feeds use .omarchy/upstream.sh. This PR auto-merges once
the build checks pass. A failing build leaves it open for a maintainer
without holding back any other package.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge once its build checks pass.

Summary

Updates omarchy-ane from 0.5.6 to 0.5.9 and replaces the pinned SHA-256 checksum.

• The omarchy-ane package now builds from version 0.5.9.

_{Reviews (13) · Last reviewed commit: "Sync upstream (six-hourly): omarchy-ane ..." · Reviewed by Greptile}

[joshuaswarren]

[Joshua's agent] I compared #1909 with #2153 by reading both diffs and hashing both release archives. They change different packages, so #2153 does not supersede this one:

• Sync upstream (six-hourly): omarchy-ane 0.5.9-1 #1909 changes pkgbuilds/omarchy-ane/PKGBUILD: omarchy-ane 0.5.6 to 0.5.9, sha256 2fa4a59d8bfd4401d0c94bf14141adc1e045278c40785a475d458f0ecd94faf7, which matches the v0.5.9 release archive.
• omarchy-ane-dkms: update to 0.5.10 #2153 changes pkgbuilds/omarchy-ane-dkms/PKGBUILD: omarchy-ane-dkms 0.5.9 to 0.5.10, sha256 25b23017dcfb51b85c1587f9a7216a1b601144b37ab562a0c437f71d57e94b47, which matches the v0.5.10 release archive.

Each can merge on its own. Once #1909 lands, #1894 (omarchy-ane 0.5.7) is stale and can be closed. No open PR moves omarchy-ane itself to 0.5.10 yet.