I think it's potentially confusing implementation detail to some developers, provides a risk of developers configuring it wrong, and will not be common enough of an option. I may change my mind later.
Break the sandboxing page into components rather than XPC Services. XPC Services should no longer be emphasized for the Communication component because it is much more likely for apps to implement the entitlements rather than the XPC Services.
Clarify the purpose of requiring CFBundleVersion.
Clarify in Testing that debugging issue shouldn't happen with workflow we suggest.
Clarify compression suggestions.
* EdDSA migration from DSA
* No EdDSA deprecation
* Channels
* Setting feed programmatically
* Migrating to newer features using new appcast (linked from EdDSA migration)
* Extending the Appcast with custom extensions
* Migration notes from earlier versions of Sparkle 2
* Minor rewording on some pages
* Update documentation (part 1)
* Plug-in bundles & Sandboxing
* Javascript key
* sparkle:version element over attribute changes
* <link> additions (in case Sparkle uses them to fall back on, eg update not found)
* Major upgrades
* Minimum system requirement for 2.x
* Update Sparkle 2.x paths, migration notes, code signing XPC Services
* Rename 1.x and 2.x to 1 and 2 where appropriate
* Update app cast example to use edSignature and remove Test App zip
* Update copyright to include initial release year
Leave out altering code sign script without hardened runtime which isn't accurate since Sparkle builds with hardened runtime automatically before the script invocation (which may not be needed).
Mention using custom XPC Service prefix.
Zorg
Zev Eisenberg