Advanced Changelog Features

🚀Advanced Changelog Features

Experimental / Loaded Only

Understand experimental switches without assuming they currently alter output.

Command[tool.custy.changelog.advanced]

📦Category

Changelog Configuration

🚀Quick Command

[tool.custy.changelog.advanced]

---

heuristicsexperimentalfuture behavior

---

📋

Properties

3

🛡️

Generated Values

All false

⚙️

Loaded

Yes

⚠️

Applied

Not by active pipeline

Properties

📋Properties

Property	Type	Description	Default	Required
auto_detect_type	Boolean	Intended to infer a Conventional Commit type from untyped messages. Loaded into configuration but not applied by the active pipeline.	false	No
detect_breaking_changes	Boolean	Intended to add heuristic breaking detection beyond configured keywords. Loaded but not applied.	false	No
smart_formatting	Boolean	Intended for evolving spacing, grouping, duplicate reduction, and formatting heuristics. Loaded but not applied.	false	No

Generated experimental defaults

toml

[tool.custy.changelog.advanced]
auto_detect_type = false
detect_breaking_changes = false
smart_formatting = false

🛡️Do not rely on these switches

The resolver creates an AdvancedConfig model, but the active generator and processing pipeline do not consume these fields. Enabling them currently does not provide a stable documented output contract.

Use stable alternatives

• Write explicit Conventional Commit types instead of relying on inference.
• Use changelog.breaking.keywords for active breaking detection.
• Use documented rendering fields and edit the project Jinja template for intentional formatting changes.

Continue

🚀Related Commands

Commands commonly used together with this command.

Core

Configure active type filtering.

Breaking Changes

Configure active keyword detection.

Rendering

Configure active presentation fields.