chore(deps-dev): bump the dependencies group with 3 updates #7067
Triggered via pull request
September 15, 2025 02:03
dependabot[bot]
Status
Failure
Total duration
8m 12s
Artifacts
–
Annotations
65 errors and 16 notices
|
Test - windows-latest - Node v22.x, Webpack latest (3/4)
Process completed with exit code 1.
|
|
Test - macos-latest - Node v20.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v18.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v18.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v18.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v20.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v22.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v22.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v20.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v22.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v20.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v24.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v22.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v24.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" failed
|
|
Test - macos-latest - Node v24.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" 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)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (3/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" 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)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (1/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" failed
|
|
Test - windows-latest - Node v22.x, Webpack latest (2/4)
The operation was canceled.
|
|
Test - windows-latest - Node v22.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" 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)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (4/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" 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)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
An interface can only extend an object type or intersection of object types with statically known members.
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
Object literal may only specify known properties, and 'retries' does not exist in type 'Options'.
|
|
Test - windows-latest - Node v18.x, Webpack latest (2/4)
The strategy configuration was canceled because "test.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" 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.windows-latest_22_x_3_4_l" failed
|
|
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 (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 (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 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 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
|
|
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 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 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 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 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 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 (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 (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 (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
|