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?
- Read the action on GitHub for inputs, outputs, and the quick start
- Add it from GitHub Marketplace
- Copy a ready-made workflow for a changelog release, a tag message, a custom title, or attached files
- Ask the docs or open DeepWiki







