🔧 Changes
Section titled “🔧 Changes”Readable changelog validation check name
Section titled “Readable changelog validation check name”Jun 5, 2026 · @mavam, @codex · #27
The changelog validation workflow now appears as Validate changelog in GitHub status checks instead of the raw job id validate, making required branch checks easier to identify.
Changelog entry history guidance
Section titled “Changelog entry history guidance”The bundled agent skill now tells release automation to preserve published changelog history while still allowing clearly related unreleased entries to be merged before release.
Historical release notes, manifests, and released entry files are treated as immutable records, with edits reserved for explicit severe publication fixes. For unreleased work, agents now check whether a related entry already exists and merge it instead of creating duplicate changelog entries, reconciling the title, type, and description while appending distinct authors, pull request numbers, and components.
The merge guidance now requires a clear relationship based on the user-facing outcome, not just nearby implementation work, shared files, authors, or PR timing. Ambiguous changes should get a separate entry, and unrelated unreleased entries must remain untouched.