Clarify the first-run package update invitation - #304
Merged
Merged
Conversation
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.
What changed and why
First login shows a normal-priority invitation to update supported Linux packages and discover optional features. It no longer claims that an update is available or that pinned runtime/boot files will advance. The narrow reviewed patch preserves Wi-Fi setup and other notifications. Package-lock changes are already covered exactly by PR #292 and are omitted here.
Release split 10/15 from
prepare-0.5.0at7240777, including main's audio fix at226ca68. This PR follows preceding PR in the release stack and targetsmain. Merge the stack in order with merge commits; squash/rebase merging requires restacking the remaining PRs. The complete stack plus package-lock PR #292 reproduces the original release tree exactly.Testing
git diff --check codex/release-050-ghostty..HEAD: passed.python3 -m unittest discover -s guest/tests -p test_first_run_update_notification.py: passed.python3 guest/tests/verify.py --source /private/tmp/try-omarchy-release-split/omarchy-v4.0.4: passed.The assembled original release tree passed
make test TEST_JOBS=2on macOS 27.0.1 / Apple Silicon, including 402 Swift tests. Pinned-source checks use Omarchy v4.0.4 atc668141e9c42b13c80c9ca4ea108e11708c5e8a5. Extraction and testing used an isolated worktree; the original checkout/build was untouched.Guest/runtime component builds and app/guest visual checks were not rerun during extraction. CI builds and macOS 15/26 results remain pending.