Repository navigation
Follow Omarchy's x86 / aarch64 / aarch64-apple platform names - #26
Merged
Merged
Conversation
omacom/omarchy now names Apple Silicon aarch64-apple, so comparing omarchy-hw-platform with apple-silicon skipped all of omarchy-mac's setup. omarchy-hw-apple-silicon answers on runtimes before and after the rename; tests stub the new names and keep one old-runtime case. Bump to 0.1.2.
Owner provisioning and reset ask the Apple predicate. The snapshot hook still needs the detector's answer to tell a failure apart, so it accepts aarch64-apple and the older apple-silicon.
runtime_platform maps them to a pre-rename runtime's names, so the suite runs against either.
omacom/omarchy#14431 merged with the platform rename. The package-resolution fixtures take the platforms' names and read the renamed Apple list.
scottjones
approved these changes
Oct 10, 2026
This was referenced Oct 10, 2026
scottjones
added a commit
that referenced
this pull request
Oct 10, 2026
Brings in #26's platform names. omarchy-mac stays at #12's 0.2.0, above main's 0.1.2, in the version file and the README. The runtime pin stays on omacom/omarchy#14675's head 00fcc451, which sits on main's pinned quattro e1b0e5e9b; its note now says so. #12's one platform check, the unit's ExecCondition, already goes through omarchy-hw-apple-silicon. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
omacom/omarchy#14431 merged into quattro (e1b0e5e9b) with the platform rename:
omarchy-hw-platformnow printsx86,aarch64oraarch64-apple. omarchy-mac and omarchy-mac-boot compared its output withapple-silicon, so on the new runtimeomarchy-mac-setup-systemand the battery, Wi-Fi, Electron, Steam, provisioning and snapshot gates all took the not-a-Mac path.omarchy-hw-apple-siliconinstead of comparing strings. Both the new runtime and the pre-rename one (5397950a2) ship it, and pacman updates these packages and the runtime separately, so it is the one predicate that works on both. Upstream kept it as a hidden alias for exactly these packages. Once omarchy-mac can require a runtime that shipsomarchy-hw-aarch64-apple, the calls move to that name and the alias can go.omarchy-mac-setup-systemruns the detector first, then the predicate.omarchy-mac-snapshot-checkmatchesaarch64-apple | apple-silicon.runtime_platform, so the suite runs against either runtime.platform=apple-silicon. That is what the installer's image builder writes, and the old runtime's detector rejectsaarch64-apple, so nothing here writes the new value.platforms/aarch64-appleandplatforms/aarch64, and they readinstall/omarchy-aarch64-apple.packages.Test plan
Run in an Arch Linux ARM container, the way CI runs it:
omarchy-mac/test/all,omarchy-mac-boot/test/allandtest/integration/allwithOMARCHY_TEST_RUNTIMEat e1b0e5e9b: all pass (92 / 224 / 53 ok)OMARCHY_TEST_RUNTIMEat 5397950a2 (pre-rename): all pass with the same countscheck-scope,check-architecture-gates,check-fixture-drift: passtools/package-resolution/test/check-test.sh, plustools/package-resolution/check --runtimeat e1b0e5e9b against the live databases: both fixtures pass