Skip to content
This repository was archived by the owner on Nov 3, 2020. It is now read-only.

Fix for finding updates via Sparkle#300

Merged
orta merged 10 commits intomasterfrom
sparkle_four
May 1, 2016
Merged

Fix for finding updates via Sparkle#300
orta merged 10 commits intomasterfrom
sparkle_four

Conversation

@orta
Copy link
Copy Markdown
Member

@orta orta commented Apr 30, 2016

( 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.

@orta
Copy link
Copy Markdown
Member Author

orta commented May 1, 2016

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

Comment thread app/Fragaria.podspec.json
{
"name": "Fragaria",
"version": "1.0.1",
"version": "1.0.2",
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I bumped this on purpose, to make sure that it fixed a CP 1.0b4 issue

@orta
Copy link
Copy Markdown
Member Author

orta commented May 1, 2016

This also includes a fix for #305 - which was about setting a UI element's property on a BG thread

@orta orta merged commit f8eadca into master May 1, 2016
@nwest nwest deleted the sparkle_four branch May 1, 2016 12:13
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant