Skip to content

feat(Fsdk/Process): introduce simple overload #2378

feat(Fsdk/Process): introduce simple overload

feat(Fsdk/Process): introduce simple overload #2378

Triggered via pull request June 15, 2026 08:33
Status Success
Total duration 20m 50s
Artifacts

CI.yml

on: pull_request
macOS--dotnet10-and-mono
17m 33s
macOS--dotnet10-and-mono
linux-oldLTS-github--dotnet-and-newmono
7m 20s
linux-oldLTS-github--dotnet-and-newmono
linux-newLTS-vanilla--dotnet10
6m 57s
linux-newLTS-vanilla--dotnet10
windows--dotnet10
9m 14s
windows--dotnet10
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 3 warnings
windows--dotnet10: test/bin/testWarning.fsx.fs#L7
The result of this expression has type 'bool' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
windows--dotnet10: test/bin/testWarning.fsx.fs#L7
The result of this expression has type 'bool' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
macOS--dotnet10-and-mono: test/bin/testWarning.fsx.fs#L7
The result of this expression has type 'bool' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
macOS--dotnet10-and-mono: test/bin/testWarning.fsx.fs#L7
The result of this expression has type 'bool' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
windows--dotnet10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v1.7.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
macOS--dotnet10-and-mono
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v1.7.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
sanity-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-dotnet@v1.7.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/