Add isolated ARM package channels and safe switching - #379
Open
scottjones wants to merge 16 commits into
Open
scottjones wants to merge 16 commits into
scottjones wants to merge 16 commits into
Conversation
scottjones
marked this pull request as ready for review
September 9, 2026 05:47
Member
|
Before merge, please link one end-to-end run against populated stable, RC, and edge endpoints, including stable → RC → stable. Fixture coverage does not prove the published inventories and signatures line up. |
Member
|
Found two blockers:
Needs work: reject stable identities from edge manifests and publish the three channel manifests before merging. |
wesleygrimes
added
defer
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
3 participants
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.
Stable, RC and edge currently share the legacy ARM edge endpoint, so an RC cannot be isolated from stable users. This adds client support for separate channel-stable, channel-rc and channel-edge snapshots. Dev uses edge packages plus a channel-capable Mac checkout.
Switches validate the complete published inventory before changing repositories, preserve ALARM/Asahi base repositories, keep the explicitly selected compositor packages signed, and complete updates using packaged commands after leaving dev. The standalone installer and recovery helper use the matching validator. Build support preserves upstream package identities: omarchy/settings for stable and RC, and omarchy-dev/settings-dev for edge/dev.
This is a minimal compatibility backport onto quattro (291a698), separate from the broader stabilization integration in #377. Source version stays 4.0.2; a separately validated compatibility package release is needed before enabling switches back to stable. Historical 4.0.2-2 snapshots are rejected for switching because they restore the old shared-edge client.
Depends on publisher infrastructure: omarchy-mac/omarchy-pkgs-aarch64#15 and populated, validated channel endpoints. Default quattro must contain channel-capable source before fresh dev cloning can succeed. No live client has been switched and no package release is claimed by this PR.
Validation: focused channel/recovery/preflight and real-pacman selection suites, metadata and syntax passed; independent code review passed. Final full local and hosted CI validation is in progress: https://github.com/scottjones/omarchy/actions/runs/34302123798 .