Closed ZevEisenberg closed 6 years ago
Blah. Yea. I think what I really need to do here is just render this markdown as HTML and use that as the changelog. That would also fix the artifact of being able to see the master
notes here
It could be a nice enhancement to Sparkle to do this automatically, especially if it's pulling directly from your GitHub tags. But I'm not sure if it is, or if you're maintaining the change log files on a server yourself.
Right now it's just pointing the to changelog on master, which is why it includes the master one. I should instead have it point to the tags for sure, that would help at least the noise at the top
I've improved the second problem here by pointing to the changelog at the tag of the release:
Gonna close this one now that at least the info doesn't include newer stuff than what is actually in the release. We'll live with the monospacing
Any way to get Sparkle to parse Markdown?