chore: group minor dependencies into single PR#20457
Merged
comphead merged 3 commits intoapache:mainfrom Feb 21, 2026
Merged
Conversation
github-actions
Bot
added
the
development-process
Jefffrey
approved these changes
Feb 21, 2026
Contributor
Author
|
Thanks @Jefffrey it might require couple of iterations to refine the patterns |
de-bgunter
pushed a commit
to de-bgunter/datafusion
that referenced
this pull request
Mar 24, 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. --> - 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 file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
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
Ensure
object_storeandsqlparserremain easy to diagnoseThese 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.What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?