Fix npm audit vulnerability #32
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
Aupajo
requested changes
Oct 21, 2024
krismartin
force-pushed
the
upgrade/fetch-mock
branch
from
3a23190 to
1cb41f2
Compare
krismartin
force-pushed
the
upgrade/fetch-mock
branch
from
1cb41f2 to
998d60a
Compare
Aupajo
approved these changes
Oct 22, 2024
krismartin
force-pushed
the
upgrade/fetch-mock
branch
from
998d60a to
1960048
Compare
Ran `npm audit fix --force` to fix vulnerability in `fetch-mock` Bump to version 0.3.1
krismartin
force-pushed
the
upgrade/fetch-mock
branch
from
1960048 to
c253dc3
Compare
|
Closing this and will re-open to see if it fixes the merging issue |
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.
This fixes the vulnerability warning on
npm install. It also bumps the version to0.3.1