Skip to content

Conversation

@alamb
Copy link
Contributor

@alamb alamb commented Nov 14, 2025

Which issue does this PR close?

Rationale for this change

Per @xudong963 #17558 (comment) we have backported stuff into the 51 branch, so we also need to update the changelog

What changes are included in this PR?

Ran

./dev/release/generate-changelog.py 50.3.0 branch-51 51.0.0 > dev/changelog/51.0.0.md
npx prettier@2.7.1 --write             '{datafusion,datafusion-cli,datafusion-examples,dev,docs}/**/*.md'             '!datafusion/CHANGELOG.md'             README.md             CONTRIBUTING.md

And checked in the result

Are these changes tested?

By CI

Are there any user-facing changes?

@github-actions github-actions bot added the development-process Related to development process of DataFusion label Nov 14, 2025
@alamb alamb mentioned this pull request Nov 14, 2025
37 tasks
Copy link
Contributor

@zhuqi-lucas zhuqi-lucas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@alamb
Copy link
Contributor Author

alamb commented Nov 14, 2025

Thank you @zhuqi-lucas 🙏

@alamb alamb merged commit fd35a09 into apache:branch-51 Nov 14, 2025
4 checks passed
@alamb
Copy link
Contributor Author

alamb commented Nov 14, 2025

here is a PR to apply the same changes to main:

@alamb alamb deleted the alamb/changelog_tweak branch November 14, 2025 15:34
github-merge-queue bot pushed a commit that referenced this pull request Nov 14, 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 #123` indicates that this PR will close issue #123.
-->

- part of
#17558 (comment)
- 

## Rationale for this change
Forward port changes  from branch-51 to main:
- #18705

## What changes are included in this PR?

Bring changes from this PR to main
- #18705


## 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.
-->
jizezhang pushed a commit to jizezhang/datafusion that referenced this pull request Nov 15, 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 (comment)
- 

## Rationale for this change
Forward port changes  from branch-51 to main:
- apache#18705

## What changes are included in this PR?

Bring changes from this PR to main
- apache#18705


## 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.
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

development-process Related to development process of DataFusion

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants