Skip to content

[Repo Assist] Prepare release 4.6.0 — fix merge conflict in RELEASE_N… #135

[Repo Assist] Prepare release 4.6.0 — fix merge conflict in RELEASE_N…

[Repo Assist] Prepare release 4.6.0 — fix merge conflict in RELEASE_N… #135

Triggered via push March 4, 2026 09:02
Status Success
Total duration 1m 30s
Artifacts

publish.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build
The 'PackageIconUrl'/'iconUrl' element is deprecated. Consider using the 'PackageIcon'/'icon' element instead. Learn more at https://aka.ms/deprecateIconUrl
build: tests/FSharp.Control.AsyncSeq.Tests/AsyncSeqTests.fs#L2012
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#L2003
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#L2304
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#L2304
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.