Skip to content

Update dependency @storybook/test-runner to ^0.24.0 #762

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
etp-bot-mu wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency @storybook/test-runner to ^0.24.0 #762

etp-bot-mu wants to merge 1 commit into from

Conversation

@etp-bot-mu
Copy link
Collaborator

@etp-bot-mu etp-bot-mu commented Sep 1, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@storybook/test-runner ^0.19.0 → ^0.24.0 age confidence

Release Notes

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

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
🐛 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: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Renovate Bot.

@etp-bot-mu etp-bot-mu added the dependencies Pull requests that update a dependency file label Sep 1, 2025
@etp-bot-mu etp-bot-mu force-pushed the renovate-fix/storybook-test-runner-0.x branch from 3b40b62 to e3dd209 Compare September 3, 2025 08:21
@etp-bot-mu etp-bot-mu force-pushed the renovate-fix/storybook-test-runner-0.x branch from e3dd209 to 5940c77 Compare October 28, 2025 15:20
@etp-bot-mu etp-bot-mu changed the title Update dependency @storybook/test-runner to ^0.23.0 Update dependency @storybook/test-runner to ^0.24.0 Oct 28, 2025
@etp-bot-mu
Copy link
Collaborator Author

etp-bot-mu commented Oct 28, 2025 •
edited
Loading

⚠️ 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: etp-front/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/storybook
npm ERR!   dev storybook@"^8.0.5" 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" from @storybook/[email protected]
npm ERR! node_modules/@storybook/test-runner
npm ERR!   dev @storybook/test-runner@"^0.24.0" 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! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-11-11T06_21_12_750Z-debug-0.log

@etp-bot-mu etp-bot-mu force-pushed the renovate-fix/storybook-test-runner-0.x branch from 5940c77 to 48b9131 Compare November 10, 2025 11:19
@etp-bot-mu etp-bot-mu force-pushed the renovate-fix/storybook-test-runner-0.x branch from 48b9131 to 8c00db7 Compare November 11, 2025 06:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@etp-bot-mu @renovate-bot