Skip to content

build(deps): bump actions/setup-node from 4 to 5 (#254) #719

build(deps): bump actions/setup-node from 4 to 5 (#254)

build(deps): bump actions/setup-node from 4 to 5 (#254) #719

Triggered via push September 8, 2025 10:57
Status Success
Total duration 9m 57s
Artifacts

run-tests.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

6 warnings and 8 notices
P8.4 - L11.* - prefer-lowest - ubuntu-latest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
P8.4 - L11.* - prefer-lowest - ubuntu-latest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
P8.4 - L11.* - prefer-lowest - windows-latest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
P8.4 - L11.* - prefer-lowest - windows-latest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
P8.4 - L11.* - prefer-lowest - macos-latest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
P8.4 - L11.* - prefer-lowest - macos-latest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
P8.3 - L12.* - prefer-stable - windows-latest
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
P8.4 - L11.* - prefer-stable - windows-latest
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
P8.4 - L12.* - prefer-stable - windows-latest
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
P8.3 - L11.* - prefer-stable - windows-latest
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
P8.3 - L12.* - prefer-lowest - windows-latest
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
P8.3 - L11.* - prefer-lowest - windows-latest
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
P8.4 - L11.* - prefer-lowest - windows-latest
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
P8.4 - L12.* - prefer-lowest - windows-latest
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