paket pack - unexpected 3rd party version constraint when not using --lock-dependencies
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
A paket pack command should create a nuget package that will enforce a certain minimum version (but not pinned) of a 3rd party dependency.
Repro steps
- Specify the 3rd party dependency with e.g. ~> 28.3 operator
- Do a paket pack without --lock-dependencies
Expected behavior
The resulting nuget package has a restriction to at e.g. >= 28.3.0 < 29.0.0
Actual behavior
The resulting package only specifies a restriction of ≥ 0.0.0
I did not remember to have this it with other constraint operators, maybe this is only happening with the twiddle wakka operator?
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 issue with paket pack, a dependency using the ~> 28.3 constraint, and without --lock-dependencies. Inspect how paket pack translates that constraint into the generated NuGet package, then verify that the package requires >= 28.3.0 and < 29.0.0 rather than >= 0.0.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100