Skip to content

Commit b51328d

Browse files
xperiandriclaude
andcommitted
Added Copilot instruction to update FSharp.Core together with the .NET SDK
Every SDK ships its FSharp.Core in `sdk/<version>/FSharp/library-packs`, and an F# compiler older than the referenced FSharp.Core may not behave correctly, so the pinned SDK and `FSharpCoreVersion` must change in the same commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 parent 334e080 commit b51328d

1 file changed

Lines changed: 1 addition & 0 deletions

File tree

‎.github/copilot-instructions.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@
44

55
* F# 10, C# 14, .NET 10, nullability checks enabled
66
* .NET SDK roll-forward policy in #file:'global.json'; the exact SDK version is pinned in the GitHub workflows and #file:'build/Program.fs'
7+
* Never change the pinned .NET SDK version without moving `FSharpCoreVersion` in #file:'Packages.props' to the FSharp.Core version that SDK ships – the `FSharp.Core.<version>.nupkg` in `sdk/<SDK version>/FSharp/library-packs` of the installation (for example, SDK 10.0.401 ships FSharp.Core 10.1.401). A compiler older than the referenced FSharp.Core may not behave correctly (see the [FSharp.Core notes](https://github.com/dotnet/fsharp/blob/main/docs/fsharp-core-notes.md)), so the SDK and FSharp.Core versions always change together, in the same commit
78
* Common parameters specified in #file:'Directory.Build.props'
89
* Central NuGet package version management – versions go in #file:'Packages.props', not in `.fsproj` files
910
* Build: `dotnet build FSharp.Data.GraphQL.slnx`

0 commit comments

Comments
 (0)