comphead opened a new pull request, #20457:
URL: https://github.com/apache/datafusion/pull/20457
## 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
- **Reduce Dependabot PR noise without reducing coverage**
Grouping most *minor* and *patch* Cargo updates into a single PR keeps
routine churn manageable while still ensuring updates are applied regularly.
- **Keep riskier updates isolated**
*Major* version bumps can include breaking changes, so we intentionally
**do not group major updates**. This preserves **one PR per crate** for majors,
simplifying review, CI triage, and rollback.
- **Preserve existing special handling for Arrow/Parquet**
- Arrow/Parquet updates are higher impact and often coordinated, so we
keep their **minor/patch** updates grouped together for consistency.
- Arrow/Parquet **major** bumps are handled manually (and ignored by
Dependabot) to avoid surprise large-scale breakage.
- **Ensure `object_store` and `sqlparser` remain easy to diagnose**
These dependencies can have outsized downstream impact in DataFusion.
Excluding them from the catch-all group ensures their updates land as
**individual PRs**, making it easier to attribute regressions and bisect
failures.
- **Maintain targeted grouping where it’s beneficial**
Protocol-related crates (`prost*`, `pbjson*`) are commonly updated
together, so grouping their minor/patch updates reduces churn while keeping
changes cohesive.
<!--
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.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
