-
Notifications
You must be signed in to change notification settings - Fork 0
Build macOS releases on a supported Apple silicon runner only #56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -71,14 +71,15 @@ brew install --cask cdisplayagain | |
| ``` | ||
|
|
||
| The cask installs the same notarization-free bundle the release workflow | ||
| publishes for arm64 and Intel. Because the app is ad-hoc signed rather than | ||
| publishes for Apple silicon. Intel Macs get no release asset; build from source | ||
| with `make install` instead. Because the app is ad-hoc signed rather than | ||
|
Comment on lines
+74
to
+75
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win Remove the stale statement that macOS packages are unavailable. The earlier installation paragraph still says that packaged macOS releases are not available. That conflicts with the arm64 archive published by the workflow and with this cask section. Update the earlier paragraph to state that Apple silicon macOS releases are available and Intel users must build from source. 🧰 Tools🪛 LanguageTool[uncategorized] ~74-~74: Did you mean the proper noun “Apple Silicon”? (APPLE_PRODUCTS) 🤖 Prompt for AI Agents |
||
| notarized, and Homebrew quarantines every cask download, the cask clears the | ||
| quarantine flag on install. See the | ||
| [tap README](https://github.com/JoshCLWren/homebrew-tap) if you would rather | ||
| handle that yourself with `--no-quarantine`. Building from source avoids the | ||
| question entirely, since a locally built app is never quarantined. | ||
|
|
||
| #### macOS app bundle (Apple silicon or Intel) | ||
| #### macOS app bundle (build from source) | ||
|
|
||
| Build a real `cdisplayagain.app` from a clone and install it, so `.cbz`/`.cbr` | ||
| files open on double-click: | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Replace the incorrect hardware-history rationale.
Intel Macs remained in Apple’s lineup after 2020. Keep the arm64-only matrix, but describe the release policy instead of claiming that Apple silicon covers every Mac sold since 2020.
Suggested wording
📝 Committable suggestion
🤖 Prompt for AI Agents