Skip to content

build(deps): bump braces from 3.0.2 to 3.0.3 in /tests/fable #138

build(deps): bump braces from 3.0.2 to 3.0.3 in /tests/fable

build(deps): bump braces from 3.0.2 to 3.0.3 in /tests/fable #138

Triggered via pull request June 16, 2024 15:33
Status Success
Total duration 7m 52s
Artifacts

dotnet.yml

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

Annotations

24 warnings
build (ubuntu-latest, 6.0.401, 14)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-node@v2, actions/setup-dotnet@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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 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)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-node@v2, actions/setup-dotnet@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
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 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.