Repository navigation
Encounter "Unknown changelog format 'None'" when generating changelog #894
Description
Description
I have the following error starting 3.12:
poetry run cz changelog \
--file-name docs/source/changelog.md.sections \
--unreleased-version UNRELEASED_VERSION
Unknown changelog format 'None'
reverted to 3.11 works fine
Steps to reproduce
poetry run cz changelog \
--file-name docs/source/changelog.md.sections \
--unreleased-version UNRELEASED_VERSION
Current behavior
Unknown changelog format 'None'
Desired behavior
changelog well generated
Screenshots
No response
Environment
cz 3.12
Activity
anthonyfinch commentedon Nov 3, 2023
I have just been bitten by this one too. @gsemet thanks for version workaround, it was blocking our builds!
[-]Good bug title tells us about precise symptom, not about the root cause.[/-][+]Encounter "Unknown changelog format 'None'" when generating changelog on Python 3.12[/+][-]Encounter "Unknown changelog format 'None'" when generating changelog on Python 3.12[/-][+]Encounter "Unknown changelog format 'None'" when generating changelog [/+]Lee-W commentedon Dec 3, 2023
HI @gsemet @anthonyfinch , could you please provide more detail on this issue? I'm not able to reproduce it. Might need to know how the changelog looks like and what are some of the example commits
bearomorphism commentedon May 9, 2026
Triage from #1964: Still valid on master (4.15.1).
commitizen/changelog_formats/__init__.py(lines 73-78) raisesChangelogFormatUnknown('None')ifchangelog_formatisn't set and the filename's extension isn't recognised (e.g.changelog.md.sections). Workaround: setchangelog_format = "markdown"in your config. Long-term fix: better error message ("Setchangelog_formatexplicitly when using a non-standard file extension") and/or default to markdown.bearomorphism commentedon May 9, 2026
Verification update (re #1964)
Reproduced against current master (4.15.1):
cz changelog --file-name docs/source/changelog.md.sections --dry-run --unreleased-version UNRELEASED_VERSIONexits with code 29:Workaround confirmed: adding
changelog_format = "markdown"to[tool.commitizen]fixes it (exit 0, changelog generated correctly).Verdict: STILL VALID. Suggested fixes:
"Cannot infer changelog format from filename '<filename>'. Set 'changelog_format' explicitly in your config (e.g., 'markdown')."markdownwhen guessing fails (least surprising for most users).changelog_formatsetting more prominently for non-standard filename use cases.