(datafusion) branch main updated: v54 upgrade guide: Remove unreleased-note (#23331)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-merge-queue[bot] pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/datafusion.git


The following commit(s) were added to refs/heads/main by this push:
     new 35a95f26cd v54 upgrade guide: Remove unreleased-note (#23331)
35a95f26cd is described below

commit 35a95f26cdfd651225e9d845bb6a23b381a0464a
Author: Simon Vandel Sillesen <si...@gmail.com>
AuthorDate: Tue Jul 7 13:25:21 2026 +0200

    v54 upgrade guide: Remove unreleased-note (#23331)
    
    ## 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.
    -->
    
    - 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.
    -->
    
    54 is released so we can remove the note
    
    ## 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.
    -->
---
 docs/source/library-user-guide/upgrading/54.0.0.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/docs/source/library-user-guide/upgrading/54.0.0.md b/docs/source/library-user-guide/upgrading/54.0.0.md
index c71b2ccd6b..f8e7ac93c0 100644
--- a/docs/source/library-user-guide/upgrading/54.0.0.md
+++ b/docs/source/library-user-guide/upgrading/54.0.0.md
@@ -21,10 +21,6 @@
 
 ## DataFusion 54.0.0
 
-**Note:** DataFusion `54.0.0` has not been released yet. The information provided
-in this section pertains to features and changes that have already been merged
-to the main branch and are awaiting release in this version.
-
 ### `AggregateFunctionExpr::human_display()` now returns `Option<&str>`
 
 `datafusion_physical_expr::aggregate::AggregateFunctionExpr::human_display()`


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@datafusion.apache.org
For additional commands, e-mail: commits-help@datafusion.apache.org