Summary points to wrong commit

It's not clear from the Github history whether this commit was outdated from the start or what, but the commit message does not match the patch. There is some indication that the refactor took a turn for a better design though. Please fix this otherwise it's just confusing in our own git history.

Thanks for the patch. Tested on my local machine and it looks good. Please be sure to setup your dev environment for next time. :)

Prettier format + fix tag

Rebase

Rebase on D7272 to address feedback

Fix version number in the release notes

• Use jQuery objects instead of plain strings -> HTML
• Encode all strings from the blog feed

I talked with Fabien about this. Originally I did not take this route because I worried there would be too much noise. But as Fabien pointed out to me, only version numbers, chainparams, and newly added args should trigger an update to the manpages. We'll see how this goes in practice.

I'm aware there are many improvements to make here (notably the commented out ninja check) and Fabien has informed me that he has patches in flight for these. I think committing them as-is is best so we can start tracking changes from the current state.

fix typo

Ensure there is a way to provide static blog feed content to improve SEO.
CI will run this script on every deployment to ensure the content is up-to-date.

• Added miner fund value
• Made the fund information a JSON object, containing addresses and minimumvalue
• Added missing help text

Fixed tests

Use available constants

Improve test robustness according to feedback

@bot gitian-osx

@bot gitian-osx

@bot gitian-osx

Make the test more friendly to future additions

It may be necessary to sanity test tx ordering as well.

Also remove i686 from contrib/release/github-release.sh