π bug(release): include every change in Artifact Hub notes - #156
Merged
Conversation
Remove the three-entry cap so generated Chart.yaml metadata covers the complete set of pending Changesets.
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.
Summary
artifacthub.io/changesannotationRoot cause
The release-version bridge truncated pending Changesets to three entries before rewriting
Chart.yaml. The generated changelog contained all entries, but Artifact Hub metadata silently omitted later changes from the same release.User impact
Artifact Hub now receives the complete per-version change list, matching the generated changelog and GitHub release notes.
Validation
node --check .github/scripts/release/version-chart.mjsartifacthub.io/changesgit diff --check