Changelog to JSON, for coding agents.
Paste a CHANGELOG.md or a GitHub release URL. Get every version, breaking change, migration step and deprecation as structured JSON — plus an llms.txt summary your agent can read before it upgrades anything.
What it reads
The changelog you already have.
No template to adopt. If each release has a version in its heading, it converts.
Keep a Changelog
## [1.2.0] - 2024-05-01 with Added, Changed, Deprecated, Removed, Fixed and Security.
conventional-changelog
semantic-release and release-please output, with ⚠ BREAKING CHANGES and scopes.
changesets
Major, Minor and Patch Changes per package, commit hashes and thanks stripped.
GitHub releases
Release notes and auto-generated “What's Changed” lists, by conventional-commit prefix.
The output
Answers “what do I need to change?”
The same shape every LogPulse changelog serves to agents, so tools built for one work with the other.
- Breaking changes with stepsEach one gets a summary, what it affects, and the migration steps written under it.
- Deprecations with replacementsWhat's going away, what to use instead, and the version it's removed in.
- An llms.txt summaryA short plain-text digest to drop into an agent's context, newest version first.
| Field (per release) | What it holds |
|---|---|
| version | Normalized version, e.g. 2.0.0 (a leading v is dropped). |
| date | Release date as YYYY-MM-DD, when the heading or release has one. |
| breaking_changes[] | { summary, affects?, migration? } — migration is Markdown steps. |
| deprecations[] | { item, replacement?, removal_version?, note? } |
| changes | added, changed, fixed, removed, security and other lists. |
| category · summary | new | improved | fixed, and a one-line summary. |
| url · notes_markdown | Compare link or release page, and the full original notes. |
Plus latest_version, totals, an unreleased section and any warnings. Full schema in the OpenAPI spec.
From your agent or CI
Same converter, one HTTP call.
No key needed. Agents connected to the LogPulse MCP server can call convert_changelog directly.
curl "https://release-ripple-roadmap.lovable.app/api/public/v1/convert?url=https://github.com/vercel/next.js/releases/tag/v15.0.0&format=llms"curl -X POST https://release-ripple-roadmap.lovable.app/api/public/v1/convert \
-H "Content-Type: text/markdown" \
--data-binary @CHANGELOG.mdclaude mcp add --transport http logpulse https://release-ripple-roadmap.lovable.app/mcp
# then ask:
# "Convert the changelog at github.com/acme/sdk and tell me
# what breaks between 1.4 and 2.0"Endpoint: https://release-ripple-roadmap.lovable.app/api/public/v1/convert · GET with ?url=, or POST JSON { markdown | url } or a raw text/markdown body · add format=llms for plain text. Read the docs.
Questions