Update the ARM Cursor AppImage during omarchy update - #424
Open
Skeptomenos wants to merge 2 commits into
Open
Conversation
The aarch64 installer disabled in-app updates and left a pinned AppImage in place, so Cursor never moved after first install. Fetch the current linux-arm64 release and replace /opt/cursor when the recorded version is behind. Co-authored-by: Cursor <cursoragent@cursor.com>
wesleygrimes
added
the
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.
Summary
/opt/cursorand turns off in-app updates (update.mode: none). After first install,omarchy updatenever touched it, so machines stayed on the old AppImage (currently hardcoded as 2.6.20).omarchy-update-cursorto theomarchy updatepipeline (after mise). On aarch64 it fetches Cursor's linux-arm64 latest release and replaces the AppImage when/opt/cursor/versionis behind. x86_64 is a no-op (cursor-binalready moves with pacman/AUR). Missing AppImage is a no-op.omarchy-install-cursoron aarch64 now downloads the current release instead of 2.6.20 and records the version so the next update can skip a redundant download.Prior art
I could not find an existing omarchy-mac issue or PR for this. Closest related work:
update.mode: none.~/Applications, tracks GitHub release metadata, and would not refresh Omarchy's/opt/cursorinstall (Cursor is not a GitHub-release AppImage).basecamp/omarchy (
omacom/omarchy) has noomarchy-install-cursor; x86 Cursor iscursor-bin. This change belongs on omarchy-mac.Test plan
test/shell.d/update-cursor-test.sh— no-op without AppImage, no-op on x86_64, skip matching version, replace older/missing version, installer no longer pins 2.6.20test/shell.d/update-sequence-test.sh,update-lock-test.sh,update-disk-space-test.sh./test/cli(metadata for the new command)/opt/cursor/cursor.AppImage:omarchy update cursordownloads if behind, then a second run prints already installedomarchy install cursoron aarch64 is not stuck on 2.6.20Made with Cursor