Referencing latest version of Fake.Core.Process (5.22.0) nuget gives FSharp.Core downgrade warnings at compile time and throws at runtime

[knocte]

Description

Referencing latest version of Fake.Core.Process (5.22.0) gives FSharp.Core downgrade warnings at compile time. I see them this way in VS4Mac:

Then if I try to use the library, for example writing this in Program.fs:

open System

open Fake.Core

[<EntryPoint>]
let main argv =
    CreateProcess.fromRawCommand "/bin/date" []
    |> Proc.run // start with the above configuration
    |> ignore // ignore exit code
    0 // return an integer exit code

I get this exception:

Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'FSharp.Core, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (0x80131040)
File name: 'FSharp.Core, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'

I've tried to find a workaround (e.g. add an explicit nuget reference to last FSharp.Core version), to no avail.

Repro steps

1. Create new .NET5 F# Console Project in VS4Mac
2. Add Fake.Core.Process as a nuget reference, use the lib in Program.fs.

Expected behavior

It should not give any warnings about FSharp.Core, and when running the project it should just work without exceptions.

Actual behavior

See screenshot above for the warnings I get.
Also see crash pasted above.

Known workarounds

Not yet.

Related information

• Operating system: macOS Monterey 12.3.1
• VS4Mac 8.10.12
• Version of FAKE: 5.22.0
• .NETCoreRuntime:
• .NET Core Runtime info in VS4Mac about dialog:
  Runtime: /usr/local/share/dotnet/dotnet
  Runtime Versions:
  6.0.4
  6.0.3
  6.0.2
  5.0.16
  5.0.15
  5.0.13
  5.0.12
  5.0.11
  5.0.10
  5.0.9
  5.0.8
  3.1.24
  3.1.23
  3.1.22
  3.1.21
  3.1.20
  3.1.19
  3.1.18
  3.1.17