Bump springdoc-openapi to the newest #47
Merged
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
This is again trying to resolve the ELR issues when OpenHouse is pulled back to LinkedIn internal. The previous attempt was not successful as its transitive dependencies still are identified as security vulnerable:
Both of them came from
org.springdoc:springdoc-openapi-ui
1.7.0
is the newest release forspringdoc-openapi-ui
(reference: https://github.com/springdoc/springdoc-openapi)And it is still pulling
spring-hateoas:1.5.4
. Will give this a try and if failed, we will need to find workaround to allow this to happen.Changes
For all the boxes checked, please include additional details of the changes made in this pull request.
Testing
Verified the Build Scan and at least
spring-data-rest-core
is in the right security range.For all the boxes checked, include a detailed description of the testing done for the changes made in this pull request.
Additional Information
For all the boxes checked, include additional details of the changes made in this pull request.