-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix][sec] Remove dependency on out-dated commons-configuration 1.x #24562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fix][sec] Remove dependency on out-dated commons-configuration 1.x #24562
Conversation
david-streamlio
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Apurva007
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
87173ba to
7cffcf0
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #24562 +/- ##
============================================
+ Coverage 73.57% 74.34% +0.77%
- Complexity 32624 32681 +57
============================================
Files 1877 1880 +3
Lines 139502 146414 +6912
Branches 15299 16784 +1485
============================================
+ Hits 102638 108851 +6213
- Misses 28908 28936 +28
- Partials 7956 8627 +671
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
BookKeeper 4.16.7 used in branch-3.0 continues to depend on commons-configuration so this PR cannot be cherry-picked to branch-3.0. |
…pache#24562) (cherry picked from commit 2e77444) (cherry picked from commit 0510a9f)
…pache#24562) (cherry picked from commit 2e77444) (cherry picked from commit 0510a9f)
…pache#24562) (cherry picked from commit 2e77444) (cherry picked from commit 0510a9f)
|
Is it intended that upgrading to commons-configuration 2.x "leaks" commons-logging to the classpath? It did not before so it comes as a surprise in a patch release. |
Thanks for the feedback @snicoll. Yes, this is a regression. It seems that it should be excluded in pulsar-common in the similar way as commons-configuration 1.x was excluded. |
Motivation
Pulsar currently has a dependency on commons-configuration:commons-configuration:1.10 which contains a low severity vulnerability CVE-2025-46392.
BookKeeper used commons-configuration until recently. After upgrading to BookKeeper 4.17.2, there's no longer a need to depend on commons-configuration in Pulsar.
Modifications
Documentation
docdoc-requireddoc-not-neededdoc-complete