update packages #179
update packages #179
Conversation
colombod
force-pushed
the
upgrade_packages
branch
from
4f18c98 to
01ebded
Compare
|
@cartermp I think I need some holding hands on this ... |
|
I think maybe you just need to bump the global.json and the github runners? |
Global.json seems fine |
colombod
force-pushed
the
upgrade_packages
branch
from
902be3c to
ee3b457
Compare
|
Ugh. So I'm pretty sure this is a FAKE issue: fsprojects/FAKE#2753 |
|
See also: fsprojects/FAKE#2719 So if we need .NET 7+ support, we need to rip out FAKE. It's honestly not a bad idea, FAKE is typically nothing but trouble for the past several years |
| @@ -86,7 +86,7 @@ | |||
| <None Include="..\..\docs\img\logo.png" Pack="true" PackagePath="\" /> | |||
| </ItemGroup> | |||
| <ItemGroup> | |||
| <PackageReference Update="FSharp.Core" Version="4.7.2" /> | |||
| <PackageReference Include="Newtonsoft.Json" Version="12.0.3" /> | |||
| <PackageReference Update="FSharp.Core" Version="8.0.100" /> | |||
There was a problem hiding this comment.
@colombod I believe this needs to be bumped back down
| <ItemGroup> | ||
| <PackageReference Update="FSharp.Core" Version="8.0.100" /> | ||
| </ItemGroup> |
There was a problem hiding this comment.
I think we should also not pull in latest FSharp.Core here, esp. since it's an older TFM (.NET 7)
|
That could make it a problem with net interactive? |
|
Closing as dealt with in latest main |
upgrading test tfm to net7.0
upgrade to .NET Interactive and other pacakges
upgraded Newtonsoft to latest
change extension loading to use script instead of assembly scanning