Background
The placeholder/formatting engine is the most heavily used subsystem of generate-release-notes, yet it has accumulated fragmented requests across multiple releases. Several individual placeholder features have been requested (#76, #78, #80, #189, #205) alongside a known default-value defect (#297) and a broader architectural proposal (#226) to unify the system.
This epic consolidates all placeholder-related work into a single coherent release, ensuring users get a well-documented, consistent placeholder API after v1.3.0.
Goals
Subtasks
Related / References
Background
The placeholder/formatting engine is the most heavily used subsystem of
generate-release-notes, yet it has accumulated fragmented requests across multiple releases. Several individual placeholder features have been requested (#76, #78, #80, #189, #205) alongside a known default-value defect (#297) and a broader architectural proposal (#226) to unify the system.This epic consolidates all placeholder-related work into a single coherent release, ensuring users get a well-documented, consistent placeholder API after v1.3.0.
Goals
Subtasks
Related / References