chore(deps-dev): bump the dependencies group across 1 directory with 8 updates #7055
Annotations
84 errors and 16 notices
Test - ubuntu-latest - Node v24.x, Webpack latest (3/4)
Process completed with exit code 1.
|
Test - macos-latest - Node v20.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v22.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v20.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v20.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v18.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v22.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v24.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v18.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v22.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v22.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v24.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v20.x, Webpack latest (4/4)
The operation was canceled.
|
Test - macos-latest - Node v20.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v24.x, Webpack latest (4/4)
The operation was canceled.
|
Test - windows-latest - Node v24.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v22.x, Webpack latest (2/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v22.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v18.x, Webpack latest (1/4)
The operation was canceled.
|
Test - macos-latest - Node v18.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v18.x, Webpack latest (4/4)
The operation was canceled.
|
Test - macos-latest - Node v18.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v24.x, Webpack latest (3/4)
The operation was canceled.
|
Test - macos-latest - Node v24.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v22.x, Webpack latest (4/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v22.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v24.x, Webpack latest (2/4)
The operation was canceled.
|
Test - windows-latest - Node v24.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v24.x, Webpack latest (3/4)
The operation was canceled.
|
Test - windows-latest - Node v24.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v20.x, Webpack latest (1/4)
The operation was canceled.
|
Test - windows-latest - Node v20.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v20.x, Webpack latest (4/4)
The operation was canceled.
|
Test - windows-latest - Node v20.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v20.x, Webpack latest (2/4)
The operation was canceled.
|
Test - windows-latest - Node v20.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
The operation was canceled.
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v22.x, Webpack latest (3/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v22.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v24.x, Webpack latest (1/4)
The operation was canceled.
|
Test - windows-latest - Node v24.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v20.x, Webpack latest (3/4)
The operation was canceled.
|
Test - windows-latest - Node v20.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v24.x, Webpack latest (4/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v24.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v22.x, Webpack latest (3/4)
The operation was canceled.
|
Test - windows-latest - Node v22.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
The operation was canceled.
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v20.x, Webpack latest (2/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v20.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
The operation was canceled.
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v22.x, Webpack latest (1/4)
The operation was canceled.
|
Test - windows-latest - Node v22.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v22.x, Webpack latest (4/4)
The operation was canceled.
|
Test - windows-latest - Node v22.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v22.x, Webpack latest (2/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v20.x, Webpack latest (3/4)
The operation was canceled.
|
Test - windows-latest - Node v22.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v20.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v20.x, Webpack latest (1/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v20.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
The operation was canceled.
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v20.x, Webpack latest (4/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v20.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v18.x, Webpack latest (4/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v18.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - macos-latest - Node v24.x, Webpack latest (2/4)
The operation was canceled.
|
Test - macos-latest - Node v24.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v18.x, Webpack latest (3/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v18.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v24.x, Webpack latest (1/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v24.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v24.x, Webpack latest (2/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v24.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v18.x, Webpack latest (1/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v18.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v22.x, Webpack latest (1/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v22.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - ubuntu-latest - Node v18.x, Webpack latest (2/4)
The operation was canceled.
|
Test - ubuntu-latest - Node v18.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.ubuntu-latest_24_x_3_4_la" failed
|
Test - windows-latest - Node v24.x, Webpack latest (4/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v24.x, Webpack latest (2/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v24.x, Webpack latest (3/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v20.x, Webpack latest (1/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v20.x, Webpack latest (4/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v20.x, Webpack latest (2/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v24.x, Webpack latest (1/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v20.x, Webpack latest (3/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v22.x, Webpack latest (3/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v22.x, Webpack latest (1/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v22.x, Webpack latest (4/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v22.x, Webpack latest (2/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
|