ysskrishna logoysskrishna

Release from Changelog or Tag

The changelog section you already wrote becomes the GitHub Release.

Release from Changelog or Tag banner
Built with
GitHub Marketplace Actions
DevOps & Infrastructure
GitHub Actions
Bash
Details
FreeMIT licenseCreated November 18, 2026Updated November 19, 2026
Share this product

The tag is pushed. The release page is still an empty box.

You already wrote what changed. Then GitHub asks for a title and a body, and someone pastes the wrong section, or pastes nothing. The next person opens the release and cannot tell what shipped.

Release from Changelog or Tag turns the section you already wrote, or the message on an annotated tag, into that GitHub Release.

The notes you wrote become the release. Nothing extra gets invented.

What you get

  • The matching version, not the whole file. A tag such as v1.2.3 uses the changelog section for 1.2.3. Headings with or without brackets both count, in the Keep a Changelog style.
  • A hard stop when the notes are empty. If that section is missing or blank, the job fails. It does not publish a release with nothing in it.
  • Your tag message, when you prefer it. Use the annotated tag instead of the changelog and the message you wrote at tag time becomes the body. Signing blocks are left out. A lightweight tag has no message, so that choice fails on purpose.
  • Files you already built. Attach the artifacts from earlier steps by listing each path. Each file needs its own filename.
  • A link the next step can use. The run reports the release URL, and whether it created a new release or left an existing one alone.
  • Free and open source. MIT licensed. Listed on GitHub Marketplace as Release from Changelog or Tag.

Picture the release

For example, you commit the version section, push the tag, and leave the workflow to it. It publishes that section as the release body. The title defaults to "Release" plus the tag. If a release for that tag is already there, the run skips it and leaves the title, body, and files unchanged.

Ready to try it?

Frequently asked questions

Why not just paste the notes into GitHub myself?

You can, once. The miss is the second time: the wrong section, a blank body, or a release that does not match the tag you pushed. This step uses the version you already tagged and refuses to publish when that text is missing or empty.

Which part of the changelog becomes the release?

Only the section for that version. A tag such as v1.2.3 matches a heading for 1.2.3, with or without brackets, in the style Keep a Changelog uses. The heading itself, later sections, and trailing reference links stay out of the body.

Can I use the message on the tag instead?

Yes. Point the step at the annotated tag and the message you wrote when you created the tag becomes the release body, without signing blocks. A lightweight tag has no message, so that mode fails instead of inventing notes.

Will it create the git tag for me?

No. You push the tag first. The action only creates the GitHub Release for a tag that is already there.

What if that release already exists?

The run skips it. The existing title, body, and attached files stay as they are. A rerun does not patch a half-finished upload.

Can I attach files I built in the workflow?

Yes. Build them in earlier steps, then list each file by its path. Every file needs its own filename. Wildcards are not supported.

Is it free?

Yes. It is open source under the MIT license and listed on GitHub Marketplace.

Do I need to be a developer?

You need a GitHub repo where you can edit workflows and push a tag. The README shows the workflow to add. This page stays out of the YAML.

Continue exploring

ProductGitHub MarketplaceGitingest Action

Gitingest Action

Repo-to-text digests in your workflow: stats, folder tree, and file contents ready for an LLM.
GitHub Marketplace Actions
GitHub Actions
Git
JavaScript
ProductGitHub MarketplacePyPI Package Stats Action

PyPI Package Stats Action

PyPI download counts in your workflow run, with a summary table you can read at a glance.
GitHub Marketplace Actions
GitHub Actions
PyPI
Python
BlogCover image for How to Add PyPI Download Stats to GitHub Actions

How to Add PyPI Download Stats to GitHub Actions

GitHub Marketplace Actions
GitHub Actions
+2
4 min read
BlogCover image for Analyze Git Repositories in GitHub Actions Using Gitingest

Analyze Git Repositories in GitHub Actions Using Gitingest

GitHub Marketplace Actions
GitHub Actions
+2
4 min read
BlogCover image for OSC 7501 in Python: Tell the Terminal When Your CLI Is Working, Blocked or Done

OSC 7501 in Python: Tell the Terminal When Your CLI Is Working, Blocked or Done

Python
Python CLI
+1
3 min read
BlogCover image for caffeinate for Windows: Keep a Locked-Down Laptop Awake Without Installing Anything

caffeinate for Windows: Keep a Locked-Down Laptop Awake Without Installing Anything

DevOps & Infrastructure
PowerShell
4 min read