[Snyk] Upgrade @storybook/test-runner from 0.10.0 to 0.20.1 #45
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.
Snyk has created this PR to upgrade @storybook/test-runner from 0.10.0 to 0.20.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 262 versions ahead of your current version.
The recommended version was released 23 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-AXIOS-6032459
SNYK-JS-AXIOS-6124857
SNYK-JS-AXIOS-6671926
Release notes
Package name: @storybook/test-runner
🐛 Bug Fix
Authors: 1
Release Notes
Refactor: Align with Storybook 8.2 core package layout
This is a structural change that shouldn't really affect you. As long as you have the
storybook
dependency in your app (which you should), you're good! This change makes it so that the test-runner deduplicates Storybook dependencies, and therefore, slims down your node_modules size.Feature: Run postVisit on failures (#494)
The test-runner's postVisit hook now runs even if there are failures. This allows you to, for instance, take snapshots on component failures. You can check whether the test has failed via the
hasFailure
property in the context passed to the hook:🚀 Enhancement
📝 Documentation
Authors: 6
Release Notes
Feature: Run postVisit on failures (#494)
The test-runner's postVisit hook now runs even if there are failures. This allows you to, for instance, take snapshots on component failures. You can check whether the test has failed via the
hasFailure
property in the context passed to the hook:🚀 Enhancement
Authors: 1
🚀 Enhancement
🐛 Bug Fix
Authors: 10
🚀 Enhancement
📝 Documentation
Authors: 2
🐛 Bug Fix
@ storybook/csf
to v0.1.11 #491 (@ paulgv)Authors: 2
🐛 Bug Fix
@ storybook/csf
to v0.1.11 #491 (@ paulgv)Authors: 1
🚀 Enhancement
🐛 Bug Fix
Authors: 3
🚀 Enhancement
🐛 Bug Fix
Authors: 2
🐛 Bug Fix
Authors: 1
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: