fix(deps): upgrade swagger-ui-react
to latest 4.x.x
#12058
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.
Follow-up to #12036, where the last vulnerable UI dep was unable to be auto-fixed due to being pinned by
swagger-ui-react
Motivation
swagger-ui-react
,@braintree/santize-url
: https://security.snyk.io/vuln/SNYK-JS-BRAINTREESANITIZEURL-3330766swagger-ui-react
itself:argo-workflows/ui/yarn.lock
Line 7702 in 5c264c0
swagger-ui-react
, but it is at least a newer patch version not susceptible to the CVEModifications
upgrade
swagger-ui-react
from 4.12.0 -> 4.19.1, latest of 4.x.x@swagger
libraries for some behaviorsVerification
Tested the
/apidocs
route myself locally, see below screenshot:Future Work
I would still like to code-split out the
/apidocs
page as a separate bundle, since it is rarely used yet has a lot of deps, and I believe includes the full Swagger file as well. That should help with issues like #11970ApiDocs
andReports
components #12061