release-notes

Unreleased

The warning about the FSharp.Core binding redirects of F# projects links to an existing section of the documentation

12.0.0-alpha003 - 2026-10-26

BREAKING: Paket.Core targets net10.0 instead of netstandard2.0: the projects and scripts that reference it must target net10.0 or later, as the paket .NET tool already needs the .NET 10 runtime. FSharp.DependencyManager.Paket stays on netstandard2.0 - https://github.com/fsprojects/Paket/issues/4317
Update the NuGet client libraries from 5.11 to 7.9, along with System.Net.Http.WinHttpHandler and System.Security.Cryptography.ProtectedData
Faster framework restrictions: writing the lock files of large repositories takes a quarter of the time and allocates less than 40% of the memory it did - https://github.com/fsprojects/Paket/issues/4317
paket convert-from-nuget now updates .slnx solution files, as it does .sln ones - https://github.com/fsprojects/Paket/issues/4443
paket convert-from-nuget removes the NuGet.Config, NuGet.targets and NuGet.exe files of the root .nuget folder again, as well as the folder once it is empty: Paket 11.0 had stopped finding them. It reads and removes the NuGet.Config of the root and of the .nuget folder under the names NuGet looks for, nuget.config, NuGet.config or NuGet.Config, and the NuGet.targets and NuGet.exe of the .nuget folder whatever the case of their name, where Linux only found lowercase names
paket convert-from-nuget converts and removes nothing through a link: it skips the projects, NuGet files and solutions of the folders that are links, with a warning for each such folder, so these projects are not converted. It leaves in place a .nuget folder that is a link and the solutions that are links, and skips with a warning the solutions it cannot read or update, instead of failing
paket convert-from-nuget only removes the solution items of a .sln that are files it deletes, found by their path in any solution folder. It removed the first line naming a NuGet file of .nuget, even a project or a packages.config it kept
paket convert-from-nuget keeps the non-ASCII characters of a .sln without a BOM, which it saved in ASCII
paket generate-load-scripts keeps in the group scripts the assemblies that reference themselves, like System.Reactive 7.0, which it dropped. It also keeps, with a warning, the assemblies and packages that depend on each other, which it dropped too - https://github.com/fsprojects/Paket/issues/4458

12.0.0-alpha002 - 2026-10-17

Add support for .slnx solution files - https://github.com/fsprojects/Paket/issues/4443
Do not warn about missing "redirects: force" for FSharp.Core in projects targeting net5.0 and later - https://github.com/fsprojects/Paket/issues/4455

Paket 12 only ships as the paket .NET tool, which needs the .NET 10 runtime: paket.exe, paket.bootstrapper.exe and Mono are no longer supported. To upgrade, install Paket as a local tool (dotnet new tool-manifest if the repository has none, then dotnet tool install paket), delete .paket/paket.exe and .paket/paket.bootstrapper.exe, call dotnet paket instead of .paket/paket.exe in your build scripts, and run dotnet paket auto-restore on again if you use auto-restore. The steps are detailed in https://fsprojects.github.io/Paket/installation.html#Moving-from-paket-exe-and-the-bootstrapper. To keep paket.exe for now, remove the version line from paket.dependencies and run .paket/paket.bootstrapper.exe --self: you get the bootstrapper of Paket 11, which stays on the latest 11.x.

This release also recognizes .NET 11 and fixes the OS-specific frameworks of .NET 9 to 11 (net9.0-android, net10.0-ios...), so the next paket update may rewrite some framework restrictions in paket.lock.