BED-4840: upped swagger-ui-react package to 5.17.14 & @types/swagger-ui-react package to 4.18.3 #868
Conversation
This file contains 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
specter-flq
added
the
infrastructure
specter-flq
added
bug
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Increased version of the swagger-ui-react package to 5.17.14 so it updates the dompurify dependency which was causing failing vulnerability scan in pipeline checks. Also updated the @types/swagger-ui-react package so they are both at the latest.
Motivation and Context
To address ticket BED-4840. Vulnerability scan is failing in pipeline checks because of the dompurify package having an issue.
How Has This Been Tested?
Tested manually by running bhce.
Screenshots (optional):
Types of changes
Checklist: