Skip to content

chore(deps): update dependency @storybook/test-runner to ^0.22.0 #53

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.

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 16, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@storybook/test-runner ^0.16.0 -> ^0.22.0 age adoption passing confidence

Release Notes

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

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
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:

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

v0.19.1

Compare Source

🐛 Bug Fix
Authors: 2

v0.19.0

Compare Source

🚀 Enhancement
🐛 Bug Fix
Authors: 3

v0.18.2

Compare Source

🐛 Bug Fix
Authors: 3

v0.18.1

Compare Source

🐛 Bug Fix
Authors: 1

v0.18.0

Compare Source

🚀 Enhancement
🐛 Bug Fix
Authors: 2

v0.17.0

Compare Source

🚀 Enhancement
🐛 Bug Fix
📝 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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Apr 16, 2024

⚠ Artifact update problem

Renovate failed to update artifacts 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 WARN cli npm v10.5.2 does not support Node.js v16.20.1. This version of npm supports the following node versions: `^18.17.0 || >=20.5.0`. You can find the latest version at https://nodejs.org/.
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @napolab/typescript@1.0.0
npm WARN Found: vite@4.3.9
npm WARN node_modules/vite
npm WARN   dev vite@"^5.0.12" from the root project
npm WARN   11 more (@joshwooding/vite-plugin-react-docgen-typescript, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer vite@"^2.2.3 || ^3.0.0 || ^4.0.3" from @vanilla-extract/vite-plugin@3.8.2
npm WARN node_modules/@vanilla-extract/vite-plugin
npm WARN   dev @vanilla-extract/vite-plugin@"^3.8.0" from the root project
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @vitejs/plugin-react@3.1.0
npm WARN Found: vite@5.2.9
npm WARN node_modules/vite
npm WARN   dev vite@"^5.0.12" from the root project
npm WARN   7 more (@joshwooding/vite-plugin-react-docgen-typescript, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer vite@"^4.1.0-beta.0" from @vitejs/plugin-react@3.1.0
npm WARN node_modules/@storybook/react-vite/node_modules/@vitejs/plugin-react
npm WARN   @vitejs/plugin-react@"^3.0.1" from @storybook/react-vite@7.6.12
npm WARN   node_modules/@storybook/react-vite
npm WARN 
npm WARN Conflicting peer dependency: vite@4.5.3
npm WARN node_modules/vite
npm WARN   peer vite@"^4.1.0-beta.0" from @vitejs/plugin-react@3.1.0
npm WARN   node_modules/@storybook/react-vite/node_modules/@vitejs/plugin-react
npm WARN     @vitejs/plugin-react@"^3.0.1" from @storybook/react-vite@7.6.12
npm WARN     node_modules/@storybook/react-vite
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: vite@5.2.9
npm ERR! notsup Not compatible with your version of node/npm: vite@5.2.9
npm ERR! notsup Required: {"node":"^18.0.0 || >=20.0.0"}
npm ERR! notsup Actual:   {"npm":"10.5.2","node":"v16.20.1"}

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-16T14_13_08_609Z-debug-0.log

File name: pnpm-lock.yaml
ERROR: This version of pnpm requires at least Node.js v18.12
The current version of Node.js is v16.20.1
Visit https://r.pnpm.io/comp to see the list of past pnpm versions with respective Node.js version support.

@renovate renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from da68a20 to 0c34661 Compare May 9, 2024 11:54
Copy link
Contributor Author

renovate bot commented May 9, 2024

⚠️ Artifact update problem

Renovate failed to update artifacts 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 warn cli npm v11.1.0 does not support Node.js v16.20.1. This version of npm supports the following node versions: `^20.17.0 || >=22.9.0`. You can find the latest version at https://nodejs.org/.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @napolab/typescript@1.0.0
npm error Found: storybook@7.6.20
npm error node_modules/storybook
npm error   dev storybook@"^7.0.9" from the root project
npm error
npm error Could not resolve dependency:
npm error peer storybook@"^0.0.0-0 || ^8.2.0 || ^8.3.0-0 || ^8.4.0-0 || ^8.5.0-0 || ^8.6.0-0 || ^9.0.0-0" from @storybook/test-runner@0.22.0
npm error node_modules/@storybook/test-runner
npm error   dev @storybook/test-runner@"^0.22.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-02-28T11_14_52_882Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-02-28T11_14_52_882Z-debug-0.log

File name: pnpm-lock.yaml
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 27, reused 0, downloaded 26, added 0
Progress: resolved 52, reused 0, downloaded 51, added 0
Progress: resolved 86, reused 0, downloaded 70, added 0
Progress: resolved 131, reused 0, downloaded 115, added 0
Progress: resolved 184, reused 0, downloaded 168, added 0
Progress: resolved 299, reused 0, downloaded 284, added 0
Progress: resolved 392, reused 0, downloaded 391, added 0
Progress: resolved 464, reused 0, downloaded 463, added 0
Progress: resolved 585, reused 0, downloaded 531, added 0
Progress: resolved 596, reused 0, downloaded 543, added 0
Progress: resolved 683, reused 0, downloaded 630, added 0
Progress: resolved 778, reused 0, downloaded 707, added 0
Progress: resolved 825, reused 0, downloaded 756, added 0
Progress: resolved 842, reused 0, downloaded 759, added 0
Progress: resolved 885, reused 0, downloaded 761, added 0
Progress: resolved 930, reused 0, downloaded 761, added 0
Progress: resolved 952, reused 0, downloaded 799, added 0
Progress: resolved 1016, reused 0, downloaded 883, added 0
Progress: resolved 1057, reused 0, downloaded 969, added 0
undefined
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

This error happened while installing the dependencies of vitest@1.2.2
 at @vitest/runner@1.2.2

Your Node version is incompatible with "registry.npmjs.org/p-limit/5.0.0".

Expected version: >=18
Got: v16.20.1

This is happening because the package's manifest has an engines.node field specified.
To fix this issue, install the required Node version.
Progress: resolved 1173, reused 0, downloaded 1060, added 0

@renovate renovate bot changed the title chore(deps): update dependency @storybook/test-runner to ^0.17.0 chore(deps): update dependency @storybook/test-runner to ^0.18.0 May 9, 2024
@renovate renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from 0c34661 to 110185e Compare June 22, 2024 14:04
@renovate renovate bot changed the title chore(deps): update dependency @storybook/test-runner to ^0.18.0 chore(deps): update dependency @storybook/test-runner to ^0.19.0 Jun 22, 2024
@renovate renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from 110185e to fc1c3e9 Compare November 28, 2024 13:43
@renovate renovate bot changed the title chore(deps): update dependency @storybook/test-runner to ^0.19.0 chore(deps): update dependency @storybook/test-runner to ^0.20.0 Nov 28, 2024
@renovate renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from fc1c3e9 to a353f23 Compare December 20, 2024 12:04
@renovate renovate bot changed the title chore(deps): update dependency @storybook/test-runner to ^0.20.0 chore(deps): update dependency @storybook/test-runner to ^0.21.0 Dec 20, 2024
@renovate renovate bot force-pushed the renovate/storybook-test-runner-0.x branch from a353f23 to 703ccde Compare February 28, 2025 11:15
@renovate renovate bot changed the title chore(deps): update dependency @storybook/test-runner to ^0.21.0 chore(deps): update dependency @storybook/test-runner to ^0.22.0 Feb 28, 2025
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