Skip to content

ci: remove unsupported filter_unconventional release-plz key#43

Merged
takaebato merged 1 commit into
masterfrom
fix/release-plz-invalid-key
Jun 28, 2026
Merged

ci: remove unsupported filter_unconventional release-plz key#43
takaebato merged 1 commit into
masterfrom
fix/release-plz-invalid-key

Conversation

@takaebato

Copy link
Copy Markdown
Owner

Problem

PR #42 added filter_unconventional = false to release-plz.toml, but that key is not supported by release-plz 0.3.159 (the latest release — it only exists in unreleased release-plz). Since #42 merged, the release-plz workflow on master now fails to parse the config:

unknown field `filter_unconventional`, expected one of `header`, `body`, `trim`,
`commit_preprocessors`, `postprocessors`, `sort_commits`, `link_parsers`,
`commit_parsers`, `protect_breaking_commits`, `tag_pattern`

Fix

Remove the unsupported key, restoring a valid config so release-plz works again.

Follow-up (separate)

The original goal — including pre-convention (non-type:) commits like #31/#33 and the external #7/#9 in the changelog — has no released config/upgrade fix (the toggle is unreleased). It is a one-time historical-backlog gap; future commits are all conventional (PR-title lint). We'll handle that gap manually rather than via config.

🤖 Generated with Claude Code

filter_unconventional is not a valid release-plz.toml field in release-plz 0.3.159 (the latest release); it exists only in unreleased release-plz. PR #42 merged it and broke config parsing on master. This restores a valid config.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

✅ PR title follows the Conventional Commits spec.

@takaebato takaebato merged commit b608298 into master Jun 28, 2026
8 checks passed
@takaebato takaebato deleted the fix/release-plz-invalid-key branch June 28, 2026 09:41
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.

1 participant