convert-from-nuget silently upgrades mismatched versions
Open
Nobody has claimed this yet.
need diagnostic info/warn/error
nuget-convert
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Given two packages.config files as per below, a lock file is generated that silently removes the "lower" version of the dependency.
<?xml version="1.0" encoding="utf-8"?>
<packages>
<package id="PetaPoco" version="5.1.153" targetFramework="net452" />
</packages>
<?xml version="1.0" encoding="utf-8"?>
<packages>
<package id="PetaPoco" version="1.9.0" targetFramework="net452" />
</packages>
Output lock file: -
remote: https://www.nuget.org/api/v2
PetaPoco (5.1.153)
I'm not sure what the expected behaviour is, but I imagine it's not to lose the 1.9.0 version.
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
Reproduce the conversion using the two packages.config examples and inspect the generated lock file. Start from the convert-from-nuget entry point and trace how mismatched PetaPoco versions are resolved. Done means the behavior for both versions is explicit and covered by an appropriate regression test or documented resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100