Skip to content

Generate the release notes automatically - #8

Merged
raszi merged 2 commits into
mainfrom
ci/release-changelog
Sep 19, 2026
Merged

raszi merged 2 commits into
mainfrom
ci/release-changelog

Conversation

@raszi

@raszi raszi commented Sep 19, 2026 •

Copy link
Copy Markdown
Member

GitHub can build the release notes from the pull request labels. This branch adds two files.

.github/release.yml groups the pull requests into categories that follow the conventional changelog format. The categories match the labels of the repository: feat, fix, perf, revert, docs, refactor, style, test, build, ci, and chore. Every other pull request goes into "Other changes".

.github/workflows/release.yml has two jobs. After each merge to main, the first job replaces a draft release with the title "Unreleased". The draft shows the upcoming changes before a real release. After a push of a v* tag, the second job publishes the release and removes the stale draft.

Do not publish the "Unreleased" draft. It would create a tag with the name unreleased. To make a release, push a tag such as v0.3.0.

@raszi raszi added the ci Change the continuous integration configuration. label Sep 19, 2026
@raszi raszi changed the title Add the release changelog configuration Generate the release notes automatically Sep 19, 2026
@raszi
raszi merged commit 0612849 into main Sep 19, 2026
4 checks passed
@raszi
raszi deleted the ci/release-changelog branch September 19, 2026 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Change the continuous integration configuration.

Development

Successfully merging this pull request may close these issues.

1 participant