Release DataFusion `50.2.0` (minor)

[AdamGS]

Is your feature request related to a problem or challenge?

• Follow on to Release DataFusion 50.1.0 (September 2025) Release DataFusion 50.1.0 (minor) #17594

There are some things that we may way to backport into the 50.0.0 line, and this ticket tracks doing so.

Steps

• Update version and changelog
• Test with DataFusion Python
• Test with DataFusion Comet
• Test with delta.rs:
• Test Vortex
• Test with iceberg-rust:
• Test with LakeSail:
• Test with parquet viewer
• Test with datafusion-materialized-views
• Voting Thread
• Publish to crates.io
• Create ticket for next release:

Potential Content:

Minor Features

• Improved Decimal support:
  • Support Decimal32/64 types #17501
  • avg(distinct) support for decimal types #17560
  • More decimal 32/64 support - type coercsion and misc gaps #17808

Bug Fixes

• Docs.rs build is broken for 50.1.0 #17889 / Fix docs.rs build: Replace auto_doc_cfg with doc_cfg #17845

Backport PR list:

• [branch-50] Backport: avg(distinct) support for decimal types (#17560) #17885
• [branch-50] Backport: Fix docs.rs build: Replace auto_doc_cfg with doc_cfg #17890
• Making CI green [branch-50] Backport: fix typos & pin action hashes (#17855) #17892
• [Branch-50] Backport: Support Decimal32/64 types (#17501) #17907
• [branch-50] Backport: More decimal 32/64 support #17908

[alamb]

I am happy to run this release process, unless @xudong963 or another PMC member wants to

[AdamGS]

Happy to help with anything I can do, I can start backporting changes once 50.1.0 is out.

[xudong963]

I can run this release process. I plan to leave the issue for 2 days to see if anyone else wants other PRs included.

[alamb]

It looks like there are a few PRs to backport but then we'll be ready to go

[AdamGS]

I have the second PR in the decimal open in my fork, once the first one merges I can open a PR targeting the branch (unless there's some github UI magic I'm missing, couldn't figure out another way to do that).

edit: Added the docs fix backport PR to the top here.

[AdamGS]

Seems like some typos sneaked into main, whats the policy here? I can fix them but seems like if they made it in its fine to keep them there for now, as I do see that upstream someone already fixed them.

[alamb]

Seems like some typos sneaked into main, whats the policy here? I can fix them but seems like if they made it in its fine to keep them there for now, as I do see that upstream someone already fixed them.

I think we should fix them in the branch so we can get a clean CI run. Maybe as a second PR 🤔

[AdamGS]

I'll open a PR later today