Skip to content

chore(deps): update dependency @storybook/test-runner to v0.24.3#458

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/storybook-test-runner-0.x
Open

chore(deps): update dependency @storybook/test-runner to v0.24.3#458
renovate[bot] wants to merge 1 commit intomainfrom
renovate/storybook-test-runner-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Mar 27, 2026

This PR contains the following updates:

Package Change Age Confidence
@storybook/test-runner 0.19.10.24.3 age confidence

@coderabbitai: ignore


Release Notes

storybookjs/test-runner (@​storybook/test-runner)

v0.24.3

Compare Source

🐛 Bug Fix
Authors: 1

v0.24.2

Compare Source

🐛 Bug Fix
Authors: 1

v0.24.1

Compare Source

🐛 Bug Fix
Authors: 3

v0.24.0

Compare Source

🚀 Enhancement
🐛 Bug Fix
Authors: 3

v0.23.0

Compare Source

🚀 Enhancement

In Storybook 9, the accessibility addon has been enhanced with automated reporting capabilities and the Test-runner has out of the box support for it. If you have @storybook/addon-a11y installed, as long as you enable them via parameters, you will get a11y checks for every story:

// .storybook/preview.ts

const preview = {
  parameters: {
    a11y: {
      // 'error' will cause a11y violations to fail tests
      test: 'error', // or 'todo' or 'off'
    },
  },
};

export default preview;

If you had a11y tests set up previously for Storybook 8 (using axe-playwright and the test-runner hooks), you can uninstall axe-playwright and remove all the code from the test-runner hooks, as they are not necessary anymore.

🐛 Bug Fix
Authors: 2

v0.22.1

Compare Source

🐛 Bug Fix
Authors: 1

v0.22.0

Compare Source

🚀 Enhancement
🐛 Bug Fix
Authors: 4

v0.21.3

Compare Source

🐛 Bug Fix
Authors: 1

v0.21.2

Compare Source

🐛 Bug Fix
Authors: 1

v0.21.1

Compare Source

🐛 Bug Fix
Authors: 2

v0.21.0

Compare Source

🚀 Enhancement
🐛 Bug Fix
Authors: 3

v0.20.1

Compare Source

🐛 Bug Fix
Authors: 1

v0.20.0

Compare Source

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:

const config: TestRunnerConfig = {
  async postVisit(_page, context) {
    if(context.hasFailure) {
      console.log('problems!')
      // do a snapshot, write a log, or anything you like
    }
  },
}

🚀 Enhancement
📝 Documentation
Authors: 6


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Copy Markdown
Contributor Author

renovate bot commented Mar 27, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: cuculus@0.1.0
npm ERR! Found: storybook@8.4.4
npm ERR! node_modules/storybook
npm ERR!   dev storybook@"8.4.4" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer storybook@"^0.0.0-0 || ^10.0.0 || ^10.0.0-0 || ^10.1.0-0 || ^10.2.0-0 || ^10.3.0-0 || ^10.4.0-0" from @storybook/test-runner@0.24.3
npm ERR! node_modules/@storybook/test-runner
npm ERR!   dev @storybook/test-runner@"0.24.3" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /runner/cache/others/npm/_logs/2026-03-27T18_31_15_978Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-27T18_31_15_978Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants