chore: update npm dependencies #396
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
jamaljsr
added a commit
that referenced
this pull request
Aug 3, 2022
It turns out that the `dependabot.yml` config file only applies to *version* updates, not *security* updates. When I added this file in #396, the bot decided to open PRs for some of our production dependencies, even if there isn't a security issue with those packages. I don't like the automated PRs because it turns into a bunch of spam in the repo. I'm deleting this file to turn off the dependabot version updates.
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 PR updates the React and Storybook dependencies.
It also adds a
dependabot.ymlconfig file to instruct it to ignore security issues for packages listed underdevDependencies. The PRs #385 and #393 that dependabot created are for for child dependencies of Storybook. After updating the@storybook/*packages to the latest version, the vulnerable versions of those packages are still included. However, that code is never bundled in the production app build and therefore does not pose an actual security risk. They can be safely ignored.