Skip to content

[Repo Assist] eng: update Microsoft.NET.Test.Sdk from 17.12.0 to 18.4.0 #203

[Repo Assist] eng: update Microsoft.NET.Test.Sdk from 17.12.0 to 18.4.0

[Repo Assist] eng: update Microsoft.NET.Test.Sdk from 17.12.0 to 18.4.0 #203

Triggered via pull request April 19, 2026 00:22
Status Success
Total duration 1m 36s
Artifacts

pull-request.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/[email protected], actions/setup-node@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: tests/FSharp.Control.AsyncSeq.Tests/AsyncSeqTests.fs#L4479
The result of groupByAsync must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: tests/FSharp.Control.AsyncSeq.Tests/AsyncSeqTests.fs#L4470
The result of groupByAsync must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: tests/FSharp.Control.AsyncSeq.Tests/AsyncSeqTests.fs#L4457
The result of groupByAsync must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: tests/FSharp.Control.AsyncSeq.Tests/AsyncSeqTests.fs#L2106
The result of groupBy must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: tests/FSharp.Control.AsyncSeq.Tests/AsyncSeqTests.fs#L2097
The result of groupBy must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: src/FSharp.Control.AsyncSeq/AsyncSeq.fs#L2728
The result of groupByAsync must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.
build: src/FSharp.Control.AsyncSeq/AsyncSeq.fs#L2728
The result of groupByAsync must be consumed with a parallel combinator such as AsyncSeq.mapAsyncParallel. Sequential consumption will deadlock because sub-sequence completion depends on other sub-sequences being consumed concurrently.