Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move old updates to old_updates in generate_appcast #2228

Merged
merged 8 commits into from
Aug 15, 2022

Conversation

zorgiepoo
Copy link
Member

@zorgiepoo zorgiepoo commented Aug 14, 2022

Move old updates to a non-hidden directory in generate_appcast which won't be as confusing. There is now a --auto-prune-update-files option to automatically remove files from this directory. For safety, files won't be automatically pruned. Also take release notes files in account as well.

Misc Checklist

  • My change requires a documentation update on Sparkle's website repository
  • My change requires changes to generate_appcast, generate_keys, or sign_update

Only bug fixes to regressions or security fixes are being backported to the 1.x (master) branch now. If you believe your change is significant enough to backport, please also create a separate pull request against the master branch.

Testing

I tested and verified my change by using one or multiple of these methods:

  • Sparkle Test App
  • Unit Tests
  • My own app
  • Other (please specify)

Tested that old update files are moved in new directory and release note files are moved too. Tested files are pruned automatically using --auto-prune-update-files

macOS version tested: 12.5 (21G72)

Also add comments to explain why certain policies were made.
Now we only automatically move old update files aside. If the user passes --auto-prune-update-files we will also remove the old update files automatically.
@zorgiepoo zorgiepoo added this to the 2.3 milestone Aug 14, 2022
@zorgiepoo zorgiepoo merged commit 80a5b80 into 2.x Aug 15, 2022
@zorgiepoo zorgiepoo deleted the generate-appcast-refinements branch August 15, 2022 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant