Skip to content

chore: Update version 54.1.0, add changelog (#23689) - #23764

Merged
mbutrovich merged 3 commits into
apache:mainfrom
mbutrovich:54.1_changelog
Jul 21, 2026
Merged

chore: Update version 54.1.0, add changelog (#23689)#23764
mbutrovich merged 3 commits into
apache:mainfrom
mbutrovich:54.1_changelog

Conversation

@mbutrovich

@mbutrovich mbutrovich commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

Rationale for this change

What changes are included in this PR?

-Cherry pick #23689 from branch-54 that updated changelog and version to 54.1.0.

Are these changes tested?

Existing CI.

Are there any user-facing changes?

Minor version bump.

@github-actions github-actions Bot added documentation Improvements or additions to documentation development-process Related to development process of DataFusion labels Jul 21, 2026

@comphead comphead 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.

Thanks @mbutrovich LGTM!

Please check fmt

@mbutrovich

Copy link
Copy Markdown
Contributor Author

Thanks @mbutrovich LGTM!

Please check fmt

Done, thanks!

@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.71%. Comparing base (050046a) to head (af8a6de).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #23764      +/-   ##
==========================================
- Coverage   80.71%   80.71%   -0.01%     
==========================================
  Files        1089     1089              
  Lines      368750   368748       -2     
  Branches   368750   368748       -2     
==========================================
- Hits       297631   297618      -13     
- Misses      53375    53382       +7     
- Partials    17744    17748       +4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@mbutrovich
mbutrovich added this pull request to the merge queue Jul 21, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Jul 21, 2026
@mbutrovich
mbutrovich added this pull request to the merge queue Jul 21, 2026
Merged via the queue into apache:main with commit eef1017 Jul 21, 2026
39 checks passed
@mbutrovich
mbutrovich deleted the 54.1_changelog branch July 21, 2026 17:39
kosiew pushed a commit to kosiew/datafusion that referenced this pull request Aug 12, 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.
-->

- Partially addresses apache#22547.

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

-Cherry pick apache#23689 from `branch-54` that updated changelog and version
to 54.1.0.

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

Existing CI.

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

Minor version bump.
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.

3 participants