docs-changelog

Automate release changelog generation by providing version, TIME, and raw changelog data as inputs to produce standardized changelog artifacts. The process applies template-driven outputs to format latest, preview, and full changelog sections consistently across releases.

Standardized changelog templates require three inputs: version, TIME, and BODY containing raw changelog data. These inputs are parsed to produce a consistent What's Changed list and a stable Full Changelog link for each release artifact.

Format changelogs for stable and preview releases by applying template-driven outputs that enforce version-path rules. The rules distinguish nightly builds, minor versions ending in .0, and patch releases to generate appropriate changelog sections for each workflow.

Version-path rules for changelog artifacts enforce specific patterns: nightly builds, minor versions ending in .0, and patch releases. These rules ensure correct artifact generation and indexing across latest, preview, and per-version documentation.

This changelog automation fits release management workflows for software teams publishing stable and preview releases. It updates index, latest, and per-version changelog artifacts by enforcing version-path rules and applying consistent template-driven outputs.

Template-driven changelog generation requires all three inputs—version, TIME, and BODY—to function correctly. It enforces version-path rules strictly, meaning releases must follow nightly, .0-ending minor, or patch patterns to produce valid changelog artifacts.