Pinned version in nuspec for .NET Core projects
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
I'm not sure it's related to paket, but I'll try.
The thing is that I want to keep pinned version constraint from paket.dependencies when running dotnet pack.
If I use standard PackageReference approach I just need to specify version as [1.0.0] and then it will get to nuspec just like that.
But If I use paket, then no matter how I specify pinned constraint in dependencies file (just 1.0, = 1.0 or even [1.0]) the version in nuspec is still just 1.0. Which means to NuGet >= 1.0.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the difference between a pinned constraint in paket.dependencies and the generated nuspec when running dotnet pack. Trace how Paket constraints are translated into nuspec dependency versions, then check whether existing tests cover pinned NuGet constraints. Done means a pinned constraint such as [1.0] remains pinned in the generated nuspec rather than becoming >= 1.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100