chore(deps): bump commons-io to 2.22.0 for RequireUpperBoundDeps - #1734
Merged
Conversation
Tika 3.3.1 transitively requires commons-io 2.22.0 while the parent BOM still managed 2.21.0, which failed maven-enforcer RequireUpperBoundDeps on delivery-tier-distribution (and any reactor module resolving the same tree). Align the managed version with Tika's requirement. Co-Authored by Grok Build using grok-4.5 with agent Grok.
natechadwick
approved these changes
Aug 1, 2026
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
Reviewed by ling-3.0-flash:free · Input: 68.1K · Output: 6.2K · Cached: 285.1K Review guidance: REVIEW.md from base branch |
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.
Summary
commons.io.versionfrom 2.21.0 → 2.22.0.maven-enforcer-pluginRequireUpperBoundDeps failures ondelivery-tier-distribution(and the same dependency tree elsewhere).Root cause
After Tika 3.3.1 (#1733), the tree includes:
while the BOM still managed 2.21.0, which is below the highest requested version. Other transitive pins (commons-net 2.20.0, csrfguard 2.18.0, etc.) were already below the managed floor and were not the failure.
Change
commons.io.versionSingle-line change in root
pom.xml.delivery-tier-suitealready consumes${commons.io.version}from the parent.Test plan
cd deliverytiersuite/delivery-tier-suite/delivery-tier-distribution && ../../../mvnw validate— enforcer (including RequireUpperBoundDeps) exit 0clean installbeyond enforcer validation of the failing moduleRisk
Low: patch-level commons-io bump to the version already required by managed Tika. No API/source changes.
Co-Authored by Grok Build using grok-4.5 with agent Grok.