NPM audit fixes #1372
Merged
NPM audit fixes #1372
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
✅ Deploy Preview for fdc3 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
bingenito
approved these changes
Sep 26, 2024
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.
Applying NPM audit fixes to FDC3, toolbox/fdc3-workbench and website. FDC3 and toolbox/fdc3-workbench get clean audits afterwards (and build correctly), while the website is improved.
However, the website still reports 20 vulnerabilities (14 moderate, 6 high) - the fix for these is to upgrade to Docusaurus 3.5.2, which is a major update with breaking changes, see: https://docusaurus.io/docs/migration/v3
I've raised a separate issue for that ypdate: #1371