Closed aaronraimist closed 6 years ago
To use Sparkle's more advanced features like delta updates (only download the parts of the app that actually changed) you definitely need the full history in the appcast. If you don't want to use those, I'm not sure. You might be able to get away with having just the latest version in the appcast.
One thing, is this code currently doesn't create a new appcast.xml file, it just updates the existing one. Maybe you could just put an appcast.xml file in .ci
or something with a fake version where the sparkle:version
is 1 or something.
As far as GitHub releases, you don't have to use that but I think it does make sense to have tags for every version.
Yeah, you're maybe right about about the GitHub tags actually. It's not so insane as long as it's confined to releases on the release
branch.
I've made some updates which I'll push back into the PR but at the moment it seems that the machine version isn't incrementing:
| SET_GITHUB_RELEASE_HTML_LINK | https://github.com/neilalexander/seaglass/releases/tag/0.0.480-release-d1ff2b8
| SET_GITHUB_RELEASE_RELEASE_ID | 13031878
| BUILD_NUMBER | 1
/Users/distiller/seaglass/fastlane/actions/sparkle_add_update.rb:30:in `run': [!] You must update the machine version to be above 477! (RuntimeError)
Close #54 Close #19