ci: Report changelog format problems rather than failing on them - #9
Merged
Conversation
validation_level: error turned psake/PowerShellBuild's CI red on main immediately. The action enforces more than the Keep a Changelog section vocabulary: it also applies a SemVer rule that a patch release may contain only Fixed and Security sections, since Added or Changed would warrant a minor bump. PowerShellBuild's 0.6.2, 0.7.2 and 0.7.3 each violate it. Those are releases already published. Recategorising their entries now would misdescribe what shipped, and cannot change the version numbers they shipped under, so the finding is real but not actionable by editing the file. Reporting keeps the finding visible without blocking every consumer on history none of them can fix. A repository that is clean can raise its own level later. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01U1Jhu7fgTRJq7LK5MuKteE
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #8, which turned
psake/PowerShellBuild'smainred immediately.validation_level: errorwas the wrong level to start at. The action enforces more than the Keep a Changelog section vocabulary — it also applies a SemVer rule that a patch release may contain onlyFixedandSecuritysections, sinceAddedorChangedwould warrant a minor bump.PowerShellBuild's history violates it three times:
Those are releases already published. Recategorising their entries now would misdescribe what actually shipped, and cannot change the version numbers they shipped under. The finding is real and worth knowing — the project did ship features in patch releases — but it is not fixable by editing the changelog.
Reporting keeps it visible without blocking every consumer on history none of them can repair. A repository whose history is clean can raise its own level later; that is a per-repository decision rather than an org-wide one.
How this got through: #8 was verified against a hand-written script that checked section vocabulary and heading format. When the action replaced that script, the extra rules it brings were never re-verified against a real changelog before merging. Verified the wrong artifact.
🤖 Generated with Claude Code
https://claude.ai/code/session_01U1Jhu7fgTRJq7LK5MuKteE