Upgrade to Sparkle 2 API #3
Open
Conversation
This file contains 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
|
@vadi2 this part needs to be merged first. |
|
Corresponding change: Mudlet/Mudlet#7499 |
vadi2
approved these changes
Oct 25, 2024
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.
Major changes in the API are outlined here: https://sparkle-project.org/documentation/upgrading/
Support for notification on launch after update was removed from Sparkle 2, so taking it out here.
Feeds are now 100% set in Info.plist (previously they had been passed in to SparkleAutoUpdater as well as set in the plist).
Setting them manually via -setFeedURL: has been deprecated, so removed that, and added the recommended action to remove them from the host bundle on init, if they exist in earlier installs.