[branch-52] Bump to 52.3.0 and changelog#20790
Merged
timsaucer merged 3 commits intoapache:branch-52from Mar 8, 2026
Merged
Conversation
github-actions
bot
added
documentation
12 tasks
Member
|
Thank you for this, but since we had another commit go in #20777 I think we need to regenerate the changelog |
timsaucer
approved these changes
Mar 8, 2026
lukekim
pushed a commit
to spiceai/datafusion
that referenced
this pull request
Mar 9, 2026
<!-- 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 #123` indicates that this PR will close issue #123. --> - Related to apache#20681 <!-- Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. --> Bumps to 52.3.0 and changelog <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> <!-- 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)? --> <!-- 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. --> --------- Co-authored-by: Haresh Khanna <hkhanna@palantir.com> Co-authored-by: Tim Saucer <timsaucer@gmail.com>
alamb
pushed a commit
to alamb/datafusion
that referenced
this pull request
Mar 10, 2026
## 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. --> - Related to apache#20681 ## Rationale for this change <!-- Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. --> ## What changes are included in this PR? Bumps to 52.3.0 and changelog <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> ## 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. --> --------- Co-authored-by: Haresh Khanna <hkhanna@palantir.com> Co-authored-by: Tim Saucer <timsaucer@gmail.com>
Contributor
|
BTW I made a PR to forward port this change to main: |
github-merge-queue bot
pushed a commit
that referenced
this pull request
Mar 12, 2026
## Which issue does this PR close? - Part of to #20681 Note I think we should wait to merge this until we officially release 53.3.0 ## Rationale for this change Keep main up to date with the most recent versions ## What changes are included in this PR? - Bumps to 52.3.0 and changelog - Forward ports #20790 - `git cherry-pick` 28d012a ## Are these changes tested? by CI ## Are there any user-facing changes? New version. Co-authored-by: Haresh Khanna <kh.haresh@gmail.com> Co-authored-by: Haresh Khanna <hkhanna@palantir.com> Co-authored-by: Tim Saucer <timsaucer@gmail.com> Co-authored-by: Oleks V <comphead@users.noreply.github.com>
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
3 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?
Rationale for this change
What changes are included in this PR?
Bumps to 52.3.0 and changelog
Are these changes tested?
Are there any user-facing changes?