Repository navigation
build(release): Enable craft's auto changelog - #163
Merged
Merged
Conversation
Without a changelog policy craft defaults to "none", so recent GitHub releases (1.9.0-1.11.0) were published with empty bodies. The github target takes the release body from the changelog file, so "auto" makes craft write CHANGELOG.md from merged PRs at prepare time, the same way our other library repos do. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
giovanni-guidini
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
GitHub releases have empty bodies.
.craft.ymlsets no changelog policy, so craft defaults tononeand skips the changelog. Craft's github target can only take the release body from the changelog file, so it publishes an empty release.Approach
Set
changelog.policy: auto, matching our other craft-released repos (craft, sentry, devservices, …). Oncraft prepare, craft writes a section built from merged PRs intoCHANGELOG.md(creating the file on the first release), commits it with the version bump, and the github target uses that section as the release body. Entries are grouped by conventional-commit type, since there's no.github/release.yml.The next release will cover everything since
1.11.0. Earlier releases are not backfilled.🤖 Generated with Claude Code