fix: generate release notes from commit range to list contributions for all release types#211
Merged
Conversation
Copilot
AI
changed the title
fix: generate release notes from default branch to list contributions for backport releases
fix: generate release notes from default branch to list all contributions
May 29, 2026
Copilot created this pull request from a session on behalf of
Flix6x
May 29, 2026 14:57
View session
Flix6x
requested changes
May 29, 2026
Copilot
AI
changed the title
fix: generate release notes from default branch to list all contributions
fix: generate release notes from commit range to list contributions for all release types
May 29, 2026
Coverage Report for CI Build 26665239964Coverage remained the same at 96.176%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
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.
Release notes for cherry-pick/backport tags (like v0.9.1) are empty because GitHub's note-generation API finds PRs by matching commits in the range
previous_tag…new_tag— a cherry-pick commit has a different SHA from the original merge commit, so nothing appears.Changes
.github/workflows/release.yml: Replacegenerate_release_notes: trueonsoftprops/action-gh-releasewith a Python script that walks the git log in theprevious_tag…current_tagrange on whichever branch the tag lives, extracts PR numbers from commit messages (the(#NNN)squash-merge pattern, which cherry-pick commits preserve), fetches PR details via the GitHub API, and categorises them according to the label config in.github/release.yml. This gives the right set of PRs for both release types:main): shows all PRs merged since the previous tag.0.9.x): shows only the cherry-picked PRs, compared against the previous lower version tag — not against the HEAD ofmain.