Enable requireUpperBoundDeps Maven enforcer rule#26717
Merged
Merged
Conversation
thll
marked this pull request as ready for review
July 22, 2026 08:03
The only consumer (the openapi-description command) exclusively uses the OpenAPI 3 parser. Depending on swagger-parser-v3 directly drops the legacy Swagger 1.x/2.0 converter chain of unmaintained transitive libraries and removes the need to manage swagger-annotations. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
[skip ci]
bernd
approved these changes
Jul 23, 2026
bernd
left a comment
bernd
left a comment
Member
There was a problem hiding this comment.
Thank you! I didn't run a smoke test using production artifacts because the e2e-tests are green.
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.
Enables the
requireUpperBoundDepsenforcer rule, which fails the build when atransitive dependency resolves to a lower version than another dependency on the
classpath declares it needs — silent downgrades of this kind have caused runtime
breakage before.
Note: this change was mostly automated, using Claude Code.
Newly managed (previously unmanaged; Maven resolved these below what other
dependencies require — versions chosen as the highest declared requirement in the
tree, not latest):
reactor-core3.7.19 —mcp-corewon resolution with 3.7.0 whileazure-corerequires ≥ 3.7.18 (a genuine runtime risk)
jsr3053.0.2 /error_prone_annotations— theguice-bomimport silently pins2015-era versions via
guice-parentjboss-logging3.6.3.Final — Jersey 4.0.2 declares 3.6.1 (built againsthibernate-validator 8.x), but we run hibernate-validator 9.x which needs 3.6.3
proto-google-common-protos,gson,opentelemetry-semconv,org.jetbrains:annotations,azure-json— pairwise version disagreementsbetween third-party dependencies (grpc vs. google-cloud, siddhi vs. google-cloud,
selenium vs. google-cloud, kotlin-stdlib vs. amazon-kinesis-client, msal4j vs.
azure-core)
Moved, versions unchanged:
guava,caffeine,commons-io,HdrHistogram,antlr4-runtimeand theopentelemetry-bomimport move fromgraylog-project-parenttograylog-parent, so the storage plugins and theenterprise repo (which don't inherit
graylog-project-parent) resolve the sameversions as the server.
Removed:
okhttp-jvmentry (included inokhttp-bomsince 5.1)swagger-parseraggregate is replaced withswagger-parser-v3: the onlyconsumer (the
openapi-descriptioncommand) uses the OpenAPI 3 parserexclusively, so this drops the legacy Swagger 1.x/2.0 converter chain (~a dozen
unmaintained transitive libraries) and removes the need to manage
swagger-annotations/prd https://github.com/Graylog2/graylog-plugin-enterprise/pull/14934
/nocl