Bug triage: audit of open "type: bug" issues (May 2026)

[bearomorphism]

This issue tracks an audit of all 30 originally-open type: bug issues, checked against master (v4.15.1).

Note

Update 2026-05-09: All actionable bug items now have either a closing decision or an open PR. Each issue has an individual verification comment with reproduction steps, and (where applicable) a follow-up confirming the fix. The 12 open PRs each follow the AI-assisted contributions guidelines and pass the full CI matrix (Python 3.10–3.14 × Linux/macOS/Windows).

✅ Closed (10) — fixed / not-a-bug / stale

• version bump with breaking change, release candidate (rc0) didn't increment major version number #472 — closed: breaking change with rc → MAJOR works correctly on all three commit forms
• pre-commit hook does not check/support custom types (defined in config.commitizen.types) #481 — closed: cz_customize schema_pattern is now respected by cz check
• cz check range sometimes failed in GitLab CI #593 — closed: GitLab CI shallow-clone artifact, not a code bug; workaround documented
• Tests Fail Depending on tomlkit Version #628 — closed: stale; current tomlkit pin & resolved version (0.14.0) handle the original case
• Tag name validation issue on cz bump --changelog #845 — closed: TagRules handles custom tag_format prefixes correctly
• Can't bump without using annotated_tag #879 — closed: cz bump no longer hangs without annotated_tag
• Help wanted: commitizen 3.x not supoort generate CHANGELOG with tag format like v1.0.0-release #950 — closed: config-only issue; matching tag_format = "v$version-release" works
• changelog is not able to recognize tags for incremental changelog #1149 — closed: same fix as Tag name validation issue on cz bump --changelog #845; tag_format = "utility/v$version" works
• Pre-commit check fails when dependency group includes are used in pyproject.toml #1500 — closed: dependency-groups parsing works on full tomlkit (>=0.8.0,<1.0.0) pin range
• cz bump crashes with version_provider=cargo on workspace virtual manifest (missing [package] / TypeError on version.workspace) #1732 — closed: cargo workspace virtual manifest works; PR already landed

🔧 Open PR (12) — awaiting review

Issue	PR	Title
#1164	#1966	yaml unicode preservation
#1615	#1967	${devrelease} substitution in tag_format
#1530	#1969	skip bump commit when nothing to commit
#466	#1970	cz_customize commit_parser default
#1614	#1972	widen prerelease/devrelease tag regex (semver2)
#894	#1973	clearer error when changelog format can''t be inferred
#956	#1975	reconfigure stdout to UTF-8 cross-platform
#1728	#1977	derive bump_map_major_version_zero from custom bump_map
#595	#1978	flag sibling version mismatches under --check-consistency
#1497	#1980	tolerate noisy git rev-parse output in is_git_project
#1790	#1981	workflow_dispatch trigger for pythonpublish.yml
#1772	#1983	only match bump patterns against commit title

Tip

Each PR has a Closes #... linkage so its issue auto-closes on merge. PRs #1967 and #1972 should land together (PR #1972 widens the regex that PR #1967''s substitution depends on).

🎁 Relabeled type: bug → type: feature (3) — waiting for maintainers to triage and decide

These were originally filed as bugs but are feature requests. They are not in scope for this bug triage; no PRs will be opened until maintainers triage and explicitly accept them. Leaving the checkboxes open as a reminder.

• Exclude the merged commits from the log (don't know maybe feature) #470 — exclude merge commits from changelog
• Flag to avoid creating a new commit for the bump #753 — --no-commit flag
• Configuration flag to prevent bumping with uncommitted changes #1194 — allow_dirty configuration flag

🤷 Open without PR (2) — needs design discussion

• No commits found to generate a pre-release #415 / Bump increments to new pre-release version from pre-release version when it wouldn't from final version #688 — prerelease bump behaviour: would need a design decision (and a breaking exit-code change) before a PR
• changelog does not include body or footer information #746 — body/footer in changelog: feature gap, needs a design choice (e.g. a changelog_include_body convenience flag) before implementation

---

Summary: 10 closed · 12 open with PR · 3 relabeled (waiting on maintainer triage, no PRs to be opened) · 2 left for design.

Each issue has individual triage and verification comments — happy to pull individual PRs out of this list for separate review.