Skip to content
CI

chore(deps): update npm packages to v22 #911

Sign in to view logs

chore(deps): update npm packages to v22

chore(deps): update npm packages to v22 #911

Triggered via pull request June 7, 2026 16:57
@renovaterenovate[bot]
opened #339
renovate/major-npm-packages
Status Failure
Total duration 24m 55s
Artifacts –

ci.yml

on: pull_request
Matrix: napi-smoke
Matrix: test
NAPI Build (Ubuntu E2E)
19m 30s
NAPI Build (Ubuntu E2E)
Fit to window
Zoom out
Zoom in

Annotations

10 errors, 20 warnings, and 3 notices
[chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload: napi/angular-compiler/e2e/tests/hmr-css.spec.ts#L61
2) [chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.evaluate: Test timeout of 30000ms exceeded. Call log: - waiting for locator('h1') 59 | 60 | // Verify the h1 color changed (it uses --primary-color) > 61 | const newColor = await page.locator('h1').evaluate((el) => { | ^ 62 | return getComputedStyle(el).color 63 | }) 64 | expect(newColor).toBe('rgb(255, 0, 0)') at /home/runner/work/oxc-angular-compiler/oxc-angular-compiler/napi/angular-compiler/e2e/tests/hmr-css.spec.ts:61:47
[chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload: napi/angular-compiler/e2e/tests/hmr-css.spec.ts#L0
2) [chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.
[chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload: napi/angular-compiler/e2e/tests/hmr-css.spec.ts#L61
2) [chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.evaluate: Test timeout of 30000ms exceeded. Call log: - waiting for locator('h1') 59 | 60 | // Verify the h1 color changed (it uses --primary-color) > 61 | const newColor = await page.locator('h1').evaluate((el) => { | ^ 62 | return getComputedStyle(el).color 63 | }) 64 | expect(newColor).toBe('rgb(255, 0, 0)') at /home/runner/work/oxc-angular-compiler/oxc-angular-compiler/napi/angular-compiler/e2e/tests/hmr-css.spec.ts:61:47
[chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload: napi/angular-compiler/e2e/tests/hmr-css.spec.ts#L0
2) [chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.
[chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload: napi/angular-compiler/e2e/tests/hmr-css.spec.ts#L61
2) [chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload Error: locator.evaluate: Test timeout of 30000ms exceeded. Call log: - waiting for locator('h1') 59 | 60 | // Verify the h1 color changed (it uses --primary-color) > 61 | const newColor = await page.locator('h1').evaluate((el) => { | ^ 62 | return getComputedStyle(el).color 63 | }) 64 | expect(newColor).toBe('rgb(255, 0, 0)') at /home/runner/work/oxc-angular-compiler/oxc-angular-compiler/napi/angular-compiler/e2e/tests/hmr-css.spec.ts:61:47
[chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload: napi/angular-compiler/e2e/tests/hmr-css.spec.ts#L19
1) [chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.evaluate: Test timeout of 30000ms exceeded. Call log: - waiting for locator('h1') 17 | 18 | // Capture initial computed style of h1 > 19 | const initialColor = await page.locator('h1').evaluate((el) => { | ^ 20 | return getComputedStyle(el).color 21 | }) 22 | at /home/runner/work/oxc-angular-compiler/oxc-angular-compiler/napi/angular-compiler/e2e/tests/hmr-css.spec.ts:19:51
[chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload: napi/angular-compiler/e2e/tests/hmr-css.spec.ts#L0
1) [chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.
[chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload: napi/angular-compiler/e2e/tests/hmr-css.spec.ts#L19
1) [chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.evaluate: Test timeout of 30000ms exceeded. Call log: - waiting for locator('h1') 17 | 18 | // Capture initial computed style of h1 > 19 | const initialColor = await page.locator('h1').evaluate((el) => { | ^ 20 | return getComputedStyle(el).color 21 | }) 22 | at /home/runner/work/oxc-angular-compiler/oxc-angular-compiler/napi/angular-compiler/e2e/tests/hmr-css.spec.ts:19:51
[chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload: napi/angular-compiler/e2e/tests/hmr-css.spec.ts#L0
1) [chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.
[chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload: napi/angular-compiler/e2e/tests/hmr-css.spec.ts#L19
1) [chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload Error: locator.evaluate: Test timeout of 30000ms exceeded. Call log: - waiting for locator('h1') 17 | 18 | // Capture initial computed style of h1 > 19 | const initialColor = await page.locator('h1').evaluate((el) => { | ^ 20 | return getComputedStyle(el).color 21 | }) 22 | at /home/runner/work/oxc-angular-compiler/oxc-angular-compiler/napi/angular-compiler/e2e/tests/hmr-css.spec.ts:19:51
NAPI Smoke (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@fb003b4f771bbf9c2de31d5f65c40689cc097fb5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NAPI Smoke (ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0hKMlagAAAAAuYDEfs2TUQ5zLh+6wt/XRUEhMMzBFREdFMDIxMgBFZGdl
NAPI Smoke (ubuntu-latest)
Failed to restore: Cache service responded with 400
Test (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@fb003b4f771bbf9c2de31d5f65c40689cc097fb5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0uaMlagAAAADknrNz7xpmRZ3JqWf7j3URUEhMMzBFREdFMDQxNwBFZGdl
Test (macos-latest)
Failed to restore: Cache service responded with 400
NAPI Smoke (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@fb003b4f771bbf9c2de31d5f65c40689cc097fb5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NAPI Smoke (macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0u6MlagAAAAA4qJPnnFL0SYCe66lsZ9+DUEhMMzBFREdFMDIyMgBFZGdl
NAPI Smoke (macos-latest)
Failed to restore: Cache service responded with 400
Test (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@fb003b4f771bbf9c2de31d5f65c40689cc097fb5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>016MlagAAAACQt4V74iw2R7zubKRS+q6dTEFYMzExMDAwMTE1MDIxAEVkZ2U=
Test (ubuntu-latest)
Failed to restore: Cache service responded with 400
NAPI Smoke (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@fb003b4f771bbf9c2de31d5f65c40689cc097fb5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NAPI Smoke (windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0H6QlagAAAACN7MRsGPM6QJb88LtoAk1cUEhMMzBFREdFMDExNgBFZGdl
NAPI Smoke (windows-latest)
Failed to restore: Cache service responded with 400
Test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@fb003b4f771bbf9c2de31d5f65c40689cc097fb5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Test (windows-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0RaQlagAAAABL1pxMC+SgSpPYMEdAqJauUEhMMzBFREdFMDIxMwBFZGdl
Test (windows-latest)
Failed to restore: Cache service responded with 400
NAPI Build (Ubuntu E2E)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Swatinem/rust-cache@fb003b4f771bbf9c2de31d5f65c40689cc097fb5. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
NAPI Build (Ubuntu E2E)
Failed to restore: Cache service responded with 400
NAPI Smoke (windows-latest)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Test (windows-latest)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
🎭 Playwright Run Summary
26 failed [chromium] › e2e/tests/hmr-css.spec.ts:9:3 › CSS Style HMR › modifying .css file triggers HMR update without page reload [chromium] › e2e/tests/hmr-css.spec.ts:41:3 › CSS Style HMR › CSS variable changes apply via HMR without reload [chromium] › e2e/tests/hmr-css.spec.ts:67:3 › CSS Style HMR › multiple CSS changes trigger multiple HMR updates [chromium] › e2e/tests/hmr-css.spec.ts:101:3 › CSS Style HMR › adding new CSS class via HMR works correctly [chromium] › e2e/tests/hmr-html-write-strategies.spec.ts:19:5 › HTML template HMR — write-strategy matrix › triggers HMR via "writeFile-in-place" [chromium] › e2e/tests/hmr-html-write-strategies.spec.ts:19:5 › HTML template HMR — write-strategy matrix › triggers HMR via "writeFile-with-fsync" [chromium] › e2e/tests/hmr-html-write-strategies.spec.ts:19:5 › HTML template HMR — write-strategy matrix › triggers HMR via "atomic-rename" [chromium] › e2e/tests/hmr-html.spec.ts:9:3 › HTML Template HMR › modifying .html file triggers HMR update without page reload [chromium] › e2e/tests/hmr-html.spec.ts:37:3 › HTML Template HMR › multiple template changes trigger multiple HMR updates without reload [chromium] › e2e/tests/hmr-html.spec.ts:62:3 › HTML Template HMR › modifying text content via template HMR works correctly [chromium] › e2e/tests/hmr-inline-styles.spec.ts:15:3 › Inline styles HMR › inline-style-only change in .ts triggers HMR (no reload) [chromium] › e2e/tests/hmr-inline-template.spec.ts:14:3 › Inline template HMR › inline-template-only change in .ts triggers HMR (no reload) [chromium] › e2e/tests/hmr-input-component.spec.ts:9:3 › Input Component HMR › component with inputs renders correctly on initial load [chromium] › e2e/tests/hmr-input-component.spec.ts:15:3 › Input Component HMR › CSS HMR on component with inputs preserves input bindings [chromium] › e2e/tests/hmr-input-component.spec.ts:50:3 › Input Component HMR › template HMR on component with inputs preserves input bindings [chromium] › e2e/tests/hmr-input-component.spec.ts:76:3 › Input Component HMR › multiple HMR updates on component with inputs do not corrupt inputs [chromium] › e2e/tests/hmr-multi-component.spec.ts:19:3 › Multi-component file HMR › both components render on initial load [chromium] › e2e/tests/hmr-multi-component.spec.ts:24:3 › Multi-component file HMR › inline template change in the FIRST component triggers HMR (no reload) [chromium] › e2e/tests/hmr-multi-component.spec.ts:44:3 › Multi-component file HMR › inline template change in the SECOND component triggers HMR (no reload) [chromium] › e2e/tests/hmr-multi-component.spec.ts:63:3 › Multi-component file HMR › inline styles change in the SECOND component triggers HMR (no reload) [chromium] › e2e/tests/hmr-multi-component.spec.ts:88:3 › Multi-component file HMR › a non-template/styles edit in a multi-component file triggers full reload [chromium] › e2e/tests/hmr-plain-ts.spec.ts:20:3 › Plain TS full reload › modifying a plain util .ts file triggers full page reload [chromium] › e2e/tests/hmr-ts.spec.ts:9:3 › TypeScript Component Full Reload › modifying .ts component file triggers full page reload [chromium] › e2e/tests/hmr-ts.spec.ts:37:3 › TypeScript Component Full Reload › adding new property to component triggers full reload [chromium] › e2e/tests/hmr-ts.spec.ts:61:3 › TypeScript Component Full Reload › modifying component decorator triggers full reload [chromium] › e2e/tests/hmr-ts.spec.ts:81:3 › TypeScript Component Full Reload › changing import statements triggers full reload 8 passed (16.2m)