-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FSharp.Core version warning (net7.0) #194
Comments
Yes, this was |
Ah paket has changed rules around its version. Lemme see if I can clean it up |
Opened an issue on paket as it seems they are generating a nuspec file differently fsprojects/Paket#4183 |
I think i'm gonna pull the version from nuget for the moment |
This happens for |
Fwiw, 3.2.0 does not exhibit this problem, it has the versions as |
I already pulled the official version. Please refer the paket issue I filled as that's the root cause. |
Do you mean that a new package with unlocked FSharp.Core version won't be published before upstream fixes it? Since the NuGet package is now locked to a fairly old F# version, it may prevent many people from updating until it's fixed. Would be great to have a package released with unlocked version as a quick fix! |
Yes, I'm not gonna get into the habit of hand editing nuget packages everytime I need to do deploy and this helps the ecosystem. |
- [FSharp.Core version warning](#194)
- [FSharp.Core version warning](#194). Credits @TheAngryByrd
Just published https://www.nuget.org/packages/FsToolkit.ErrorHandling/3.3.1-beta002#dependencies-body-tab can you give it a try? |
- [FSharp.Core version warning](#194). Credits @TheAngryByrd - [List.traverseValidationA and List.sequenceValidationA now preserve the order of errors](#192). Credits @ursenzler
Looking good on my end! |
- [FSharp.Core version warning](#194). Credits @TheAngryByrd - [List.traverseValidationA and List.sequenceValidationA now preserve the order of errors](#192). Credits @ursenzler - [Fixing Fable Build](#196) Credits @alfonsogarciacaro
- [FSharp.Core version warning](#194). Credits @TheAngryByrd - [List.traverseValidationA and List.sequenceValidationA now preserve the order of errors](#192). Credits @ursenzler - [Fixing Fable Build](#196) Credits @alfonsogarciacaro
Question: do we really need to force upgrade to F# Core 7.0? On NetStandard 2.1, the lowest denominator with tasks) should probably be used, which is 6.0.2, or 6.0.6 (Result additions). /cc @TheAngryByrd |
Describe the bug
Following what I suspect to be this change, I now get the following warning after upgrading to version
3.3.0
:To Reproduce
Steps to reproduce the behavior:
FsToolkit.ErrorHandling.TaskResult
version3.3.0
to anet7.0
project.Expected behavior
No warning.
Desktop:
The text was updated successfully, but these errors were encountered: