Repository navigation
Conversation
omarchy-mac-boot ships its target (type=repository, channel=stable), and this runtime gets a migration that runs omarchy-mac-migrate-bootstrap on Apple Silicon, so a tester's Mac moves onto the official packages on its next update whatever omarchy-mac-boot it has and whether or not 1790347292 already ran. It stays pending, without holding up the update, until the published package carries the target and the engine has run.
maralcbr
changed the base branch from
mac/53-engine-delivery
to
quattro-upstream
September 27, 2026 02:13
Collaborator
Author
|
Superseded by the standalone migration script in #690 (agreed with Ryan: existing Macs convert with a separate script, and the Mac packages carry no migration code). |
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
1 participant
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.
Ticket 53: the activation switch. Stacked on #602.
omarchy-mac-bootships/usr/lib/omarchy-mac/boot/migration-target(type=repository,channel=stable). Publishing anomarchy-mac-bootbuilt from this is what starts migrations on every cohort.migrations/1790461245.sh(this runtime only): on Apple Silicon,sudo omarchy-mac-migrate-bootstrap, then a machine-wide marker. It covers testers whateveromarchy-mac-bootthey have and whether 1790347292 already ran without a target. Until the activating package is published, or while preflight refuses, it exits 75: pending, the update goes on.Tests:
test/shell.d/mac-activation-migration-test.sh(non-Apple no-op, 75 and failures stay pending with their status, marker only after success, other accounts skip);mac-migrate-test.shasserts the packaged target. Boot and runtime suites in an Arch container: only the known failures.Merge this last, when the owner is ready to publish: it is the release trigger. Its runtime migration nags testers at login until the activating package is published, so publish
omarchy-mac-bootfrom this commit together with (or before) the runtime that carries the migration.Second review: covered with #602.