ZOOKEEPER-5018 Upgrade Jetty to 9.4.58.v20250814 in order to fix CVE-2025-5115 (ADDENDUM)#2351
Merged
anmolnar merged 1 commit intoapache:masterfrom Jan 28, 2026
Merged
Conversation
tisonkun
approved these changes
Jan 28, 2026
PDavid
reviewed
Jan 29, 2026
|
|
||
| <properties> | ||
| <prometheus.version>1.3.10</prometheus.version> | ||
| <jetty.version>9.4.57.v20241219</jetty.version> |
Contributor
There was a problem hiding this comment.
I know that this is already merged, just wondering: Would it maybe make sense for the Prometheus Metrics Provider to use the Jetty version declared in the root pom.xml?
Or is there a certain advantage that the Prometheus Metrics Provider declares it's own Jetty version here?
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
3 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.
Looks like I didn't notice that we have a separate version in Prometheus Metrics Provider.