You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Fable is failing in CI, may need to be updated to latest Fable 5.0 #334
Thanks for the report! I found the root cause: Microsoft.Bcl.AsyncInterfaces was pinned to 10.0.7 in FSharp.Control.AsyncSeq.fsproj, while System.Threading.Channels (using Version="*") resolved to a newer version requiring Microsoft.Bcl.AsyncInterfaces >= 10.0.11. This triggered an NU1605 package downgrade warning, which causes Fable's MSBuild project cracker to throw an unhandled exception and abort — this wasn't a Fable 5.0 compatibility issue.
I've opened a draft PR that unpins the version (matching the existing * convention already used for System.Threading.Channels). Verified locally: full dotnet test (476/476 passing) and npm test under tests/fable (78/78 passing, previously failing with the unhandled exception).
Generated by 🌈 Repo Assist, see workflow run. Learn more. Comment /repo-assist to run again
Add this agentic workflow to your repo
To install this agentic workflow, run
gh aw add githubnext/agentics/workflows/repo-assist.md@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38
Activity
dsyme commentedon Aug 24, 2026
/repo-assist Try to fix this please
github-actions commentedon Aug 24, 2026
✓ Repo Assist completed successfully, see workflow run.
Fix Fable CI build: unpin Microsoft.Bcl.AsyncInterfaces version
github-actions commentedon Aug 24, 2026
🤖 This is an automated response from Repo Assist.
Thanks for the report! I found the root cause:
Microsoft.Bcl.AsyncInterfaceswas pinned to10.0.7inFSharp.Control.AsyncSeq.fsproj, whileSystem.Threading.Channels(usingVersion="*") resolved to a newer version requiringMicrosoft.Bcl.AsyncInterfaces >= 10.0.11. This triggered anNU1605package downgrade warning, which causes Fable's MSBuild project cracker to throw an unhandled exception and abort — this wasn't a Fable 5.0 compatibility issue.I've opened a draft PR that unpins the version (matching the existing
*convention already used forSystem.Threading.Channels). Verified locally: fulldotnet test(476/476 passing) andnpm testundertests/fable(78/78 passing, previously failing with the unhandled exception).Add this agentic workflow to your repo
To install this agentic workflow, run