Skip to content

Fix for issue #517 (#518) #127

Fix for issue #517 (#518)

Fix for issue #517 (#518) #127

Triggered via push May 22, 2026 20:25
Status Success
Total duration 5m 37s
Artifacts

push.yml

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

Annotations

22 warnings and 1 notice
build (ubuntu-22.04, 8.0.124)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, NuGet/login@d22cc5f58ff5b88bf9bd452535b4335137e24544, peaceiris/actions-gh-pages@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (ubuntu-22.04, 8.0.124)
The assembly 'typeproviders/fsharp41/net8.0/FSharp.TypeProviders.SDK.dll' is not inside the 'lib' folder and hence it won't be added as a reference when the package is installed into a project. Move it into the 'lib' folder if it needs to be referenced.
build (ubuntu-22.04, 8.0.124)
The assembly 'typeproviders/fsharp41/net8.0/BasicProvider.DesignTime.dll' is not inside the 'lib' folder and hence it won't be added as a reference when the package is installed into a project. Move it into the 'lib' folder if it needs to be referenced.
build (ubuntu-22.04, 8.0.124): examples/StressProvider/StressProvider.fs#L145
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (ubuntu-22.04, 8.0.124): examples/StressProvider/StressProvider.fs#L63
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (ubuntu-22.04, 8.0.124): examples/StressProvider/StressProvider.fs#L145
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (ubuntu-22.04, 8.0.124)
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (ubuntu-22.04, 8.0.124)
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (ubuntu-22.04, 8.0.124)
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (ubuntu-22.04, 8.0.124)
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (ubuntu-22.04, 8.0.124)
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (windows-latest, 8.0.124)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-dotnet@v4, NuGet/login@d22cc5f58ff5b88bf9bd452535b4335137e24544. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (windows-latest, 8.0.124)
The assembly 'typeproviders\fsharp41\net8.0\FSharp.TypeProviders.SDK.dll' is not inside the 'lib' folder and hence it won't be added as a reference when the package is installed into a project. Move it into the 'lib' folder if it needs to be referenced.
build (windows-latest, 8.0.124)
The assembly 'typeproviders\fsharp41\net8.0\BasicProvider.DesignTime.dll' is not inside the 'lib' folder and hence it won't be added as a reference when the package is installed into a project. Move it into the 'lib' folder if it needs to be referenced.
build (windows-latest, 8.0.124): examples/StressProvider/StressProvider.fs#L145
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (windows-latest, 8.0.124): examples/StressProvider/StressProvider.fs#L63
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (windows-latest, 8.0.124): examples/StressProvider/StressProvider.fs#L145
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (windows-latest, 8.0.124)
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (windows-latest, 8.0.124)
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (windows-latest, 8.0.124)
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (windows-latest, 8.0.124)
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (windows-latest, 8.0.124)
Incomplete pattern matches on this expression. For example, the value '[_;_]' may indicate a case not covered by the pattern(s).
build (windows-latest, 8.0.124)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026