[branch-51] Update version to 51.0.0, add Changelog #18551
Merged
+794
−81
Conversation
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
github-actions
bot
added
the
development-process
github-actions
bot
added
the
documentation
mbutrovich
approved these changes
Nov 8, 2025
Contributor
mbutrovich
left a comment
mbutrovich
left a comment
There was a problem hiding this comment.
Looks right to me. Thanks @alamb!
Contributor
Author
|
Thanks @mbutrovich for the review! |
alamb
commented
Nov 8, 2025
|
|
||
| # Apache DataFusion 51.0.0 Changelog | ||
|
|
||
| This release consists of 531 commits from 128 contributors. See credits at the end of this changelog for more information. |
Contributor
Author
There was a problem hiding this comment.
128 contributors 😮 -- a new record I think!
alamb
added a commit
to alamb/datafusion
that referenced
this pull request
Nov 9, 2025
## Which issue does this PR close? <!-- We generally require a GitHub issue to be filed for all bug fixes and enhancements and this helps us generate change logs for our releases. You can link an issue to this PR using the GitHub syntax. For example `Closes apache#123` indicates that this PR will close issue apache#123. --> - part of apache#17558 ## Rationale for this change Let's update the version numbers! ## What changes are included in this PR? Update numbers and add changelog. I plan to merge this PR now and I will make a follow on PR (and forward port it to main) with final touchups ## Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> ## Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. -->
Contributor
Author
|
Thanks for the review @mbutrovich |
Contributor
Author
|
I also cherry-picked this to main as well |
35 tasks
github-merge-queue bot
pushed a commit
that referenced
this pull request
Nov 9, 2025
## Which issue does this PR close? - part of #17558 - port of #18551 ## Rationale for this change Let's update the version numbers! ## What changes are included in this PR? - forward port the change from #18551 to main ## Are these changes tested? by CI ## Are there any user-facing changes? New version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Which issue does this PR close?
51.0.0(Nov 2025) #17558Rationale for this change
Let's update the version numbers!
What changes are included in this PR?
Update numbers and add changelog.
I plan to merge this PR now and I will make a follow on PR (and forward port it to main) with final touchups
Are these changes tested?
Are there any user-facing changes?