paket pack adds wrong prerelease dependency
See original GitHub issueDescription
When paket.lock includes a prerelease package paket pack
command adds wrong dependency version to the .nupkg file
Repro steps
- Install a prerelease package. Sample entry
paket.dependencies
:
nuget Nancy prerelease
- Create a minimal
paket.template
type project
version 0.1
authors tpluscode
- Build Release
- Create package:
paket pack output nugets
Expected behavior
The reference should be >= 2.0.0-barneyrubble
Actual behavior
Actual reference in .nupkg is listed as <dependency id="Nancy" version="0.0.0-prerelease" />
Known workarounds
Adding these lines to paket.template
solves the issue
dependencies
Nancy >= LOCKEDVERSION
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
paket update fails with prerelease version specification #859
I have following version spec in paket.dependencies (package name was replaced): nuget Foo >= 1.10.301 prerelease In my nuget source, ...
Read more >The paket.dependencies file
Paket usually adds all direct and transitive dependencies that are listed in paket.references files to project files next to the respective paket.references ...
Read more >Paket Issues - Steve Ellwood - Medium
In my paket.dependencies file I added the line ... error : Could not find nuspec files in “obj\Debug” (Version: “0.5”), therefore we cannot...
Read more >net: adding a new source to Paket config
Try specifying prerelease in paket.dependencies i.e.: nuget System.CommandLine.Experimental prerelease. The available versions are listed ...
Read more >Nuget dependencies between prerelease packages
1 Answer 1 ... For me, this is a clear bug at NuGet, because even if you explicitly add a reference to PackageB...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
but that said: I thing we could change it to >= LOCKEDVERSION
for prereleases this would make sense
ok. but that’s just Nuget being dumb.