mirror of
https://github.com/ghostty-org/ghostty.git
synced 2025-07-14 07:46:12 +03:00
c33b82c634
Resolves #4730 I opted to link directly to the release notes of the updated version in the `<description>` body, i.e. in the future it would link directly v1.0.2's release notes at https://ghostty.org/docs/install/release-notes/1-0-2. This thereby implements the second option mentioned in the issue. It wasn't that much harder than the third option, but if there's any particular reason _not to_ link directly to a version's changelog page, I'll be more than happy to modify this PR and implement the third option instead - in any case, I had opened https://github.com/ghostty-org/website/pull/277 so that https://ghostty.org/docs/install/release-notes is a valid page. I also wrapped the current text `<![CDATA[ ... ]]>` just in case, as I noticed this is a pretty standard practice in other apps that use `<description>` to embed their release notes when using Sparkle - [Sparkle's documentation](https://sparkle-project.org/documentation/publishing/#embedded-release-notes) says to do this so you can use unescaped HTML.