Skip to content

Move the changelog to GitHub releases - #112

Merged
paracycle merged 1 commit into
mainfrom
ufuk/release-notes-on-github
Oct 27, 2026
Merged

paracycle merged 1 commit into
mainfrom
ufuk/release-notes-on-github

Conversation

@paracycle

Copy link
Copy Markdown
Member

Motivation

The repository keeps release notes in two places: CHANGELOG.md and the GitHub releases. The GitHub releases already contain the notes of every released version. The release workflow from #108 also creates a GitHub release with generated notes for each new tag. A separate CHANGELOG.md is then a second copy that maintainers must keep up to date.

Changes

  • Remove CHANGELOG.md.
  • Update the release steps in the README. A release no longer needs a CHANGELOG.md update. The README now points to the GitHub releases for the changes in each version.

Notes

  • The v0.2.1 entry from CHANGELOG.md is already in the v0.3.0 release.
  • The unreleased entries for the next version will be added to its GitHub release after the release runs.

The GitHub releases already contain the notes for each released version, and the release workflow generates notes for new releases. Remove CHANGELOG.md and point the README to the GitHub releases.
@paracycle
paracycle merged commit 18cc25a into main Oct 27, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants