How to convert json release data to a markdown changelog
- Step 1Structure the JSON as a releases array — Each element should have version (semver string), date (ISO-8601), and changes (object with Added, Changed, Fixed keys mapping to arrays of change description strings).
- Step 2Convert to Markdown — Paste the JSON and click Convert. Each release becomes a ## [version] – date section with grouped bullet lists for each change category present in the data.
- Step 3Add an Unreleased section if needed — Keep a Changelog convention includes an ## [Unreleased] section at the top for changes not yet released. Add this section manually above the generated content for ongoing development tracking.
- Step 4Save as CHANGELOG.md — Replace or append to your existing CHANGELOG.md file. Commit the updated changelog alongside the release commit so the file stays in sync with the tagged version.
Frequently asked questions
What is Keep a Changelog format and why should I use it?+
Keep a Changelog (https://keepachangelog.com) is a widely adopted convention for structuring CHANGELOG.md files with version sections, date headers, and categorized change lists. Most developer-facing projects use it because it is human-readable, machine-parseable, and recognized by GitHub's release notes renderer.
Can I generate GitHub Release body text from the JSON?+
Yes. After converting, copy the Markdown for a specific version section and paste it into the GitHub Release description body when creating a release. GitHub renders the Markdown with formatted headers and bullet points in the release page.
Is the release notes data uploaded to JAD Apps?+
No. The Markdown generation runs entirely in your browser. Version numbers, change descriptions, and pre-release notes are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.