Bump log4j2 from 2.21.0 to 2.25.1#19184
Conversation
e7aa42e to
82a7e2e
Compare
|
❌ Gradle check result for 82a7e2e: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
82a7e2e to
78e7fdf
Compare
|
❌ Gradle check result for 78e7fdf: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
78e7fdf to
928fa14
Compare
|
❌ Gradle check result for 928fa14: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
928fa14 to
cec34b0
Compare
|
❌ Gradle check result for cec34b0: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
db27748 to
6d1cdd1
Compare
|
❌ Gradle check result for 6d1cdd1: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
6d1cdd1 to
5422987
Compare
|
❌ Gradle check result for 5422987: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
5422987 to
06db206
Compare
|
❌ Gradle check result for 06db206: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
06db206 to
0cd8253
Compare
|
❌ Gradle check result for 0cd8253: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
0cd8253 to
897a611
Compare
|
❌ Gradle check result for 897a611: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
897a611 to
15aed40
Compare
|
❌ Gradle check result for 15aed40: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
ca5c631 to
6e1510e
Compare
|
❌ Gradle check result for 6e1510e: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
6e1510e to
7ec9ece
Compare
|
❌ Gradle check result for 7ec9ece: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
7ec9ece to
5fcf8ec
Compare
|
❌ Gradle check result for c5d6e27: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #19184 +/- ##
============================================
+ Coverage 72.85% 72.92% +0.07%
- Complexity 69794 69816 +22
============================================
Files 5673 5673
Lines 320711 320754 +43
Branches 46360 46369 +9
============================================
+ Hits 233642 233922 +280
+ Misses 68143 67863 -280
- Partials 18926 18969 +43 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
c5d6e27 to
afb6306
Compare
msfroh
left a comment
There was a problem hiding this comment.
Thanks a lot @willyborankin! Just a couple of minor comments.
afb6306 to
c30f407
Compare
Signed-off-by: Andrey Pleskach <ples@aiven.io>
| supercsv = "2.4.0" | ||
| log4j = "2.21.0" | ||
| log4j = "2.25.1" | ||
| error_prone_annotations = "2.41.0" |
There was a problem hiding this comment.
is there a reason for upgrading error_prone_annotations to 2.41.0 version when guava 33.2.1-jre brings in 2.26.1 ?
Due to this mismatch, now plugins like k-NN who uses guava has to remove error_prone_annotations so that there is no jar hell
Signed-off-by: Andrey Pleskach <ples@aiven.io>
Signed-off-by: Andrey Pleskach <ples@aiven.io> Signed-off-by: Ankit Jain <jainankitk@apache.org>
Signed-off-by: Andrey Pleskach <ples@aiven.io> Signed-off-by: Ankit Jain <jainankitk@apache.org>
Signed-off-by: Andrey Pleskach <ples@aiven.io>
Signed-off-by: Andrey Pleskach <ples@aiven.io>
This reverts commit b9c5bc7. Signed-off-by: Andrew Ross <andrross@amazon.com>
This reverts commit b9c5bc7. Signed-off-by: Andrew Ross <andrross@amazon.com>
Signed-off-by: Andrey Pleskach <ples@aiven.io>
…opensearch-project#19430) This reverts commit b9c5bc7. Signed-off-by: Andrew Ross <andrross@amazon.com>
…opensearch-project#19430) This reverts commit b9c5bc7. Signed-off-by: Andrew Ross <andrross@amazon.com>
Description
Bump log4j2 from 2.21.0 to 2.25.1
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.