Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Paket downgrades direct dependency without reason #3103
Paket resolves a direct dependency to a lower version than available, even though the latest version is also a valid resolution, with the same transitive dependency solution.
I would really like to give a reproduction sample here, but unfortunately, I only had this bug happen using our internal artifact server and packages. Instead, please try to follow my reasoning through this log, which is the result of running
Here is what I understand is happening:
See above, unfortunately I cannot provide a repro example using external projects.
Given a valid solution to version resolution, I would expect our direct dependencies to be resolved to the highest possible version.
Paket seems to always resolve to exactly one version behind.
We are working around the issue by adding a very loose version constraint to
added a commit
Mar 9, 2018
Thank you. I will take a look Am 09.03.2018 15:44 schrieb "Francis Thérien" <firstname.lastname@example.org>:…
OK, I created #3106 <#3106> which is based on #3104 <#3104> and reproduces the exact same issue we get. For additional fun, try adding additional versions of delphi-tf-latest-convert to the graph. Paket always resolves one version prior to latest :) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3103 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADgNIpylAV0-jYOi7QmM7JeXV01UEfaks5tcpVVgaJpZM4SjBdt> .