Turn your CHANGELOG.md into a shareable URL

Your changelog already exists in your repo. Publish it with one command and share the link with your team, users, or stakeholders.

The problem with changelogs

Most projects keep a CHANGELOG.md in the root of their repo. It's the source of truth for what changed and when. But sharing it? That's where things get awkward.

You could link people to the raw file on GitHub, but it renders poorly and requires a GitHub account for private repos. You could copy-paste into Notion or Confluence, but then you have two sources of truth. You could build a docs site, but that's a whole project just to share release notes.

MDtoLink skips all of that. One command, one URL.

How it works

1. Publish from your project root

mdtolink publish CHANGELOG.md --slug changelog

That's it. Your changelog is now live at a URL you can share with anyone.

2. Update it whenever you release

# After updating CHANGELOG.md with new entries
mdtolink publish CHANGELOG.md --slug changelog

Same command, same URL. The content updates in place. Anyone with the link sees the latest version.

3. Automate it in CI

# .github/workflows/release.yml
- name: Publish changelog
  run: npx mdtolink publish CHANGELOG.md --slug changelog
  env:
    MDTOLINK_API_KEY: ${{ secrets.MDTOLINK_API_KEY }}

Add it as a step in your release pipeline. Every time you tag a release, the changelog updates automatically.

Why use MDtoLink for changelogs?

Single source of truth

Your repo's CHANGELOG.md is the source. No copy-pasting, no syncing, no drift.
Readable by anyone

No GitHub account needed. No login required for readers. Just a clean, rendered markdown page.
Stable URL

The link never changes. Pin it in Slack, add it to your README, include it in your release emails.
Custom domains

On the Publisher plan, host your changelog at changelog.yourcompany.com.

Frequently Asked Questions

Can I publish a CHANGELOG.md directly from my repo?

Yes. Run mdtolink publish CHANGELOG.md from your project root. The file is published as-is, with full markdown rendering including headings, lists, code blocks, and links.

Does the URL change when I update my changelog?

No. Running mdtolink publish again with the same file updates the content in place. The URL stays the same, so any links you have shared will always point to the latest version.

Can I automate changelog publishing in CI/CD?

Yes. Use the MDtoLink REST API or CLI in your GitHub Actions, GitLab CI, or any other pipeline. Authenticate with an API key and run mdtolink publish CHANGELOG.md as a post-release step.

Can I use a custom domain for my changelog?

Yes, on the Publisher plan. Point a CNAME record to mdtolink.com and your changelog lives at something like changelog.yourcompany.com. SSL is handled automatically.

Publish your changelog in 30 seconds

Free to start. No credit card required.

Start Publishing Free Read the Docs