Skip to content

[main] Update version and changelog to 54.0.0#22855

Merged
alamb merged 5 commits into
apache:mainfrom
alamb:alamb/update_to_54
Jun 9, 2026
Merged

[main] Update version and changelog to 54.0.0#22855
alamb merged 5 commits into
apache:mainfrom
alamb:alamb/update_to_54

Conversation

@alamb

@alamb alamb commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Rationale for this change

Now that we have released version 54 we should update the version number of main to match

What changes are included in this PR?

Forward port changes from @mbutrovich :

Are these changes tested?

Are there any user-facing changes?

mbutrovich and others added 2 commits June 9, 2026 12:48
## 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.
-->

- Closes #.

## 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?

<!--
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: Andrew Lamb <andrew@nerdnetworks.org>
@alamb alamb marked this pull request as ready for review June 9, 2026 16:50
@github-actions github-actions Bot added the development-process Related to development process of DataFusion label Jun 9, 2026
@alamb alamb marked this pull request as draft June 9, 2026 16:50
@alamb alamb marked this pull request as ready for review June 9, 2026 16:55
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Jun 9, 2026

@mbutrovich mbutrovich left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM, thanks @alamb!

@alamb alamb enabled auto-merge June 9, 2026 17:02
@alamb

alamb commented Jun 9, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the review @mbutrovich

@alamb alamb added this pull request to the merge queue Jun 9, 2026
Merged via the queue into apache:main with commit 8995ce6 Jun 9, 2026
37 checks passed
@alamb alamb deleted the alamb/update_to_54 branch June 9, 2026 17:38
AdamGS pushed a commit to AdamGS/arrow-datafusion that referenced this pull request Jun 11, 2026
## Which issue does this PR close?

- part of apache#21080

## Rationale for this change

Now that we have released version 54 we should update the version number
of main to match

## What changes are included in this PR?

Forward port changes from @mbutrovich :
- c8dddb8
- 45d943d
- 7a14d12 (needed resolving)


## 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: Matt Butrovich <mbutrovich@users.noreply.github.com>
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 documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants