Skip to content

[Repo Assist] Prepare release 4.6.0 — fix merge conflict in RELEASE_NOTES.md, bump version 4.5.0 → 4.6.0 #146

[Repo Assist] Prepare release 4.6.0 — fix merge conflict in RELEASE_NOTES.md, bump version 4.5.0 → 4.6.0

[Repo Assist] Prepare release 4.6.0 — fix merge conflict in RELEASE_NOTES.md, bump version 4.5.0 → 4.6.0 #146

Triggered via pull request March 3, 2026 17:17
Status Success
Total duration 1m 34s
Artifacts

pull-request.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
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.