Skip to content

ci: fix release notes for release branches (#5597)#5699

Merged
jackye1995 merged 1 commit intolance-format:release/v1.0from
jackye1995:patch-5597
Jan 12, 2026
Merged

ci: fix release notes for release branches (#5597)#5699
jackye1995 merged 1 commit intolance-format:release/v1.0from
jackye1995:patch-5597

Conversation

@jackye1995
Copy link
Copy Markdown
Contributor

When we cherry-pick bug fixes onto release branches, we sometimes need to modify the commits to work on a new base. When we do that, we change the commit so it's not the same as the original merge commit from the PR. The GitHub release-notes API excludes these commits from the notes it generates. This PR reproduces the same change notes format, but uses the commit messages to grab the PRs, even if they have been rebased.

When we cherry-pick bug fixes onto release branches, we sometimes need
to modify the commits to work on a new base. When we do that, we change
the commit so it's not the same as the original merge commit from the
PR. The GitHub release-notes API excludes these commits from the notes
it generates. This PR reproduces the same change notes format, but uses
the commit messages to grab the PRs, even if they have been rebased.
@github-actions github-actions Bot added the ci Github Action or Test issues label Jan 12, 2026
@jackye1995 jackye1995 merged commit 40f1768 into lance-format:release/v1.0 Jan 12, 2026
3 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Github Action or Test issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants