Skip to content

fix(changelog): match the crate-prefixed tags release-plz creates #175

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sksizer merged 1 commit into from
Sep 23, 2026
Merged

fix(changelog): match the crate-prefixed tags release-plz creates #175

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion cliff.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,10 @@ conventional_commits = true
filter_unconventional = true
split_commits = false
commit_parsers = [
# A `merge: …` subject is a conventional commit as far as the parser is
# concerned, so without this the stack-merge commits form their own
# "### merge" section in the release notes.
{ message = "^merge", skip = true },
{ message = "^feat", group = "Added" },
{ message = "^fix", group = "Fixed" },
{ message = "^refactor", group = "Changed" },
Expand All @@ -65,5 +69,12 @@ commit_parsers = [
]
protect_breaking_commits = false
filter_commits = false
tag_pattern = "v[0-9].*"
# No `tag_pattern`. release-plz creates crate-prefixed tags in a workspace
# (`ontogen-v0.7.0`, `ontogen-core-v0.5.0`), and the previous pattern
# `v[0-9].*` matched none of them -- only the four legacy tags from before the
# workspace split (`v0.1.0` .. `v0.3.0`). git-cliff could then find no current
# release to bound the range and emitted an almost-empty changelog, which is
# how the 0.7.1 release PR came to list one commit out of fourteen. Unset,
# every tag counts, so the newest one bounds the range correctly; release-plz
# passes the per-package range explicitly regardless.
sort_commits = "oldest"
Loading