chore: 🤖 Update xmldom dependency resolution #693
Merged
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
Update xmldom transitive dependency resolution to avoid a security vulnerability.
|
This pull request is being automatically deployed with Vercel (learn more). boundary-ui – ./ui/admin🔍 Inspect: https://vercel.com/hashicorp/boundary-ui/3j8uMCavTgw96MRGczKdMZ3H9Kn4 boundary-ui-storybook – ./addons/rose🔍 Inspect: https://vercel.com/hashicorp/boundary-ui-storybook/CXfLhuA5B7RzoG1v5wrSteekg47K boundary-ui-desktop – ./ui/desktop🔍 Inspect: https://vercel.com/hashicorp/boundary-ui-desktop/AgnxM49Qj2BCXwrMrtA1UCkUkYBw |
gsusmi
approved these changes
Aug 9, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Update xmldom transitive dependency resolution to avoid a security vulnerability.
Readme before reviews:
The maintainer of the project is having an issue to publish the latest version on NPM, they are working on it, in the meantime they recommend to resolve the package against their GH repo. More info about it here.
I already set a reminder on my calendar to check this periodically until the issuue is resolved, then I will provide a PR to delete the resolution with gh in favour of npm.