Skip to content

build(deps): bump cross-spawn from 7.0.3 to 7.0.6 in /tests/fable #143

build(deps): bump cross-spawn from 7.0.3 to 7.0.6 in /tests/fable

build(deps): bump cross-spawn from 7.0.3 to 7.0.6 in /tests/fable #143

Triggered via push November 18, 2024 23:22
Status Success
Total duration 7m 38s
Artifacts

dotnet.yml

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

Annotations

24 warnings
build (ubuntu-latest, 6.0.401, 14)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (ubuntu-latest, 6.0.401, 14)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (ubuntu-latest, 6.0.401, 14)
The argument names in the signature 'count' and implementation 'n' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (ubuntu-latest, 6.0.401, 14)
The argument names in the signature 'source' and implementation 's' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (ubuntu-latest, 6.0.401, 14)
The argument names in the signature 'count' and implementation 'n' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (ubuntu-latest, 6.0.401, 14)
The argument names in the signature 'source' and implementation 's' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (ubuntu-latest, 6.0.401, 14)
The argument names in the signature 'predicate' and implementation 'p' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (ubuntu-latest, 6.0.401, 14)
The argument names in the signature 'source' and implementation 's1' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (ubuntu-latest, 6.0.401, 14)
The argument names in the signature 'count' and implementation 'n' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (ubuntu-latest, 6.0.401, 14)
The argument names in the signature 'source' and implementation 's' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (ubuntu-latest, 6.0.401, 14)
The argument names in the signature 'count' and implementation 'n' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (ubuntu-latest, 6.0.401, 14)
The argument names in the signature 'source' and implementation 's' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (windows-latest, 6.0.401, 14)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (windows-latest, 6.0.401, 14)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (windows-latest, 6.0.401, 14)
The argument names in the signature 'count' and implementation 'n' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (windows-latest, 6.0.401, 14)
The argument names in the signature 'source' and implementation 's' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (windows-latest, 6.0.401, 14)
The argument names in the signature 'count' and implementation 'n' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (windows-latest, 6.0.401, 14)
The argument names in the signature 'source' and implementation 's' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (windows-latest, 6.0.401, 14)
The argument names in the signature 'predicate' and implementation 'p' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (windows-latest, 6.0.401, 14)
The argument names in the signature 'source' and implementation 's1' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (windows-latest, 6.0.401, 14)
The argument names in the signature 'count' and implementation 'n' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (windows-latest, 6.0.401, 14)
The argument names in the signature 'source' and implementation 's' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (windows-latest, 6.0.401, 14)
The argument names in the signature 'count' and implementation 'n' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.
build (windows-latest, 6.0.401, 14)
The argument names in the signature 'source' and implementation 's' do not match. The argument name from the signature file will be used. This may cause problems when debugging or profiling.