Release arrow-rs / parquet Major version `56.0.0` (July 2025)

[alamb]

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

Let's keep the code flowing. Part of

• [EPIC] A collection of release tickets #7392

Release Checklist:

• Verify with downstream DataFusion tests: DRAFT: Update arrow/parquet to 56.0.0 datafusion#16690
• Release notes and bump version: Prepare for 56.0.0 release: Update version and CHANGELOG.md #8014
• Release Candidate + Vote thread: https://lists.apache.org/thread/h2l3d8gxvg78cw5lcgxotowz7mzth6kd
• Release to crates.io / approval:
• Create follow on ticket: Release arrow-rs / parquet Minor version 56.1.0 (August 2025) #7837

Needed items for release

• Remove deprecated Arrow functions #7830
• Upgrade tonic dependencies to 0.13.0 version #7377 / Upgrade tonic dependencies to 0.13.0 version (try 2) #7839
• Continued: Use Arc<[Buffer]> instead of raw Vec<Buffer> in GenericByteViewArray for faster slice #7773
• GH-7686: [Parquet] Fix int96 min/max stats #7687
• Fix RowConverter when FixedSizeList is not the last #7789

Requested items for release

• Update the parquet thrift definitions #7567
• Improvements for parquet writing performance (25%-44%) #7824
• [arrow-flight] Update prost-* crates to 0.14 #7990
• Implemented casting for RunEnd Encoding #7713

[alamb]

@etseidl, @CurtHagenlocher, @XiangpengHao @Dandandan @Xuanwo and others, given all the breaking changes we have just merged into main I am thinking we should release a 55.0.0 release in the next day or two, rather than waiting for another month to accumulate more changes.

The current schedule says "July 2025" which gives us sufficient flexibility

Is there any PRs you think we should wait for (that have breaking API changes)? These are two I can see

• Remove deprecated Arrow functions #7830
• Upgrade tonic dependencies to 0.13.0 version #7377 / Upgrade tonic dependencies to 0.13.0 version (try 2) #7839

[etseidl]

The only others I see are #7773 and #7687 (although I'm not sure the latter is breaking any more since the public API changes were reverted...now it's just a UB change).

[Dandandan]

Not a breaking change, but would maybe be nice if #7824 makes it into release.

[alamb]

The only others I see are #7773 and #7687 (although I'm not sure the latter is breaking any more since the public API changes were reverted...now it's just a UB change).

Added to the list above

Not a breaking change, but would maybe be nice if #7824 makes it into release.

Likewise added

[findepi]

#7789 is a needed item for the release, because #7705 landed with a bug that could lead to data corruption.

[alamb]

#7789 is a needed item for the release, because #7705 landed with a bug that could lead to data corruption.

👍 Added to the list