From 27176928409bb6b2aeb602fef02b1b433f9316a2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Kornel=20Lesin=CC=81ski?= Date: Fri, 19 Feb 2016 09:16:57 +0000 Subject: [PATCH] Notes for 1.14 --- documentation/upgrading/index.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/documentation/upgrading/index.md b/documentation/upgrading/index.md index e8ea927..ee0cc41 100644 --- a/documentation/upgrading/index.md +++ b/documentation/upgrading/index.md @@ -4,14 +4,20 @@ id: documentation title: Upgrading from previous versions of Sparkle --- -We strongly recommend using Sparkle 1.11.1 or later, as there have been major improvements to reliability and integrity of updates. Very old versions of Sparkle also suffer some incompatibilities with the latest OS X versions. +We strongly recommend using Sparkle 1.13.1 or later, as there have been important fixes in reliability and [security](/documentation/security) of updates. Very old versions of Sparkle also suffer some incompatibilities with the latest OS X versions. -If you're upgrading from a very old version of Sparkle we recommend using [Sparkle 1.13 or later](//github.com/{{ site.github_username }}/Sparkle/releases). The API is backwards-compatible. +If you're upgrading from a very old version of Sparkle we recommend using [Sparkle 1.14 or later](//github.com/{{ site.github_username }}/Sparkle/releases). The API is backwards-compatible. ## Upgrading to SDK 10.11 (affects all versions of Sparkle) Apps compiled with SDK 10.11 are required to use HTTPS only or configure exceptions to allow HTTP access. If you're not using HTTPS yet, please see [App Transport Security](/documentation/app-transport-security/) to ensure that users on OS X 10.11 will be able to get updates. +## Upgrading from Sparkle 1.13 and older + +Sparkle doesn't try to "fix" incorrect URLs in the appcast. URLs with any un-encoded non-ASCII characters need to use URL-encoding, e.g. `` should be changed to ``. + +JavaScript is now disabled by default when showing release notes' HTML. It can be re-enabled by setting `SUEnableJavaScript` in the app's `Info.plist`. + ## Upgrading from Sparkle 1.12 and older To work around a bug in Sparkle versions up to 1.10 we've changed bundle ID of the framework (from `org.andymatuschak.Sparkle` to `org.sparkle-project.Sparkle`).