Skip to content
PR

chore(deps): update dependency @faker-js/faker to v10 [security] #1926

Sign in to view logs

chore(deps): update dependency @faker-js/faker to v10 [security]

chore(deps): update dependency @faker-js/faker to v10 [security] #1926

Triggered via pull request September 24, 2026 23:11
@renovaterenovate[bot]
synchronize #524
renovate/npm-faker-js-faker-vulnerability
Status Failure
Total duration 19s
Artifacts –

pr.yml

on: pull_request
Test
11s
Test
E2e
14s
E2e
Preview
13s
Preview
Version Preview
12s
Version Preview
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 4 notices
Test
Command "vp install" (cwd: /home/runner/work/devtools/devtools) exited with code 1
vp install failed
Scope: all 50 workspace projects [ERR_PNPM_OUTDATED_LOCKFILE] Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/package.json Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile" Failure reason: specifiers in the lockfile don't match specifiers in package.json: * 1 dependencies are mismatched: - @faker-js/faker (lockfile: ^9.9.0, manifest: ^10.0.0)
Preview
Command "vp install" (cwd: /home/runner/work/devtools/devtools) exited with code 1
vp install failed
Scope: all 50 workspace projects [ERR_PNPM_OUTDATED_LOCKFILE] Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/package.json Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile" Failure reason: specifiers in the lockfile don't match specifiers in package.json: * 1 dependencies are mismatched: - @faker-js/faker (lockfile: ^9.9.0, manifest: ^10.0.0)
Version Preview
Command "vp install" (cwd: /home/runner/work/devtools/devtools) exited with code 1
vp install failed
Scope: all 50 workspace projects [ERR_PNPM_OUTDATED_LOCKFILE] Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/package.json Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile" Failure reason: specifiers in the lockfile don't match specifiers in package.json: * 1 dependencies are mismatched: - @faker-js/faker (lockfile: ^9.9.0, manifest: ^10.0.0)
E2e
Command "vp install" (cwd: /home/runner/work/devtools/devtools) exited with code 1
vp install failed
Scope: all 50 workspace projects [ERR_PNPM_OUTDATED_LOCKFILE] Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/package.json Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile" Failure reason: specifiers in the lockfile don't match specifiers in package.json: * 1 dependencies are mismatched: - @faker-js/faker (lockfile: ^9.9.0, manifest: ^10.0.0)
Test
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Preview
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
Version Preview
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"
E2e
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"