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.
Security fix detailed in swagger-ui's release notes.
https://github.com/swagger-api/swagger-ui/releases/tag/v3.23.11
What's this PR do/fix?
Bumps the swagger-ui dependency.
Are there unit tests? If not how should this be manually tested?
No new functionality, just a gradle dependency version change. All of the old tests should be run to verify no breaking changes between versions.
Any background context you want to provide?
Swagger-ui has a security fix that addresses a CSS-based input field value exfiltration vulnerability in this release.
What are the relevant issues?
#3131