This repository has been archived by the owner on Nov 3, 2020. It is now read-only.
Fix for finding updates via Sparkle #300
Merged
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
…s compared in Sparkle
|
Sigh, I've rebuilt this 3 times now and there's been no changes to anything that would change the actual CI process ( as changes are all at App level, as opposed to Rakefile level ) triggered it one more time, but i'm building a release off the top commit here |
| @@ -1,6 +1,6 @@ | |||
| { | |||
| "name": "Fragaria", | |||
| "version": "1.0.1", | |||
| "version": "1.0.2", | |||
There was a problem hiding this comment.
I bumped this on purpose, to make sure that it fixed a CP 1.0b4 issue
|
This also includes a fix for #305 - which was about setting a UI element's property on a BG thread |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
( rich context )
In the last few apps, we've been using the date as a SemVer for the app. This was so we could decouple builds of the app from CocoaPods releases. In practice though, Sparkle would compare our date vs CP versions, which makes it hard to use thee date. So I've moved us back to inline versions.