Update the .NET SDK in the CI builds to 6.0.300#2780
Conversation
|
Hmm, the macOS CI failed and the built output contains So now I wonder if the old version of Mono.Posix it's using maybe only has Intel CPU support? |
|
There are some integration tests in https://github.com/fsprojects/FAKE/blob/master/src/test/Fake.Core.IntegrationTests/Fake.DotNet.sdkAssemblyResolver.fs which are doing explicit things with the 6.0.10X SDK, and I start to wonder if that simply isn't going to work on ARM macs? |
|
This could help the CI failure: #2783 |
|
But it is already rebased |
|
Maybe the failure is this asking 6.0.100: ...as the CI reports it here: There are other too, e.g. here: |
|
I tried updating some of those in https://github.com/Numpsy/FAKE/commits/6.0.131/ a while ago and hit some other failures. |
|
Probably 8 is better |
|
The build at https://github.com/Numpsy/FAKE/actions/runs/10161143249 from the branch at https://github.com/Numpsy/FAKE/tree/bump_flail seems to have passed with the 6.0.30x SDK, though there are still a couple of changes n top of the SDK update in there |
Description
A minimal update to the .NET 6 SDK version, to see if it fixes the macOS/ARM CI failures discussed in #2778