feat: add GitHub Sponsors links and an App Store build configuration - #119
Merged
Merged
Conversation
Adds a Sponsor button to the repo (FUNDING.yml), a Support section to the README, and a "Sponsor on GitHub" row at the bottom of Settings -> About. App Store builds must update through the App Store and can't link to outside payment, so a new AppStore configuration defines APP_STORE and the scheme's Archive action uses it. With APP_STORE set, the update checker never contacts GitHub or surfaces a cached update, and Settings hides "Check for Updates" and the sponsor row. CI still archives with -configuration Release, so GitHub releases are unchanged.
|
🎉 This PR is included in version 2.27.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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
Sponsoring
.github/FUNDING.ymladds a Sponsor button to the repo page, linking to https://github.com/sponsors/MegaManSec.App Store build
AppStorebuild configuration (a copy of Release that definesAPP_STORE). The scheme's Archive action uses it, so Product → Archive in Xcode produces the App Store build. CI still archives with-configuration Release, so GitHub releases are unchanged.APP_STOREset,UpdateCheckernever contacts GitHub, starts no timer, and ignores any cached update from an earlier GitHub install. So the menu and Settings never show an update, and any leftover update notification is removed.PRIVACY.mdnotes that the App Store version doesn't check for updates.