You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Look at paket.lock, Octokit.fsx dependency changed from fsharp/FAKE43c4800c5f132d2c2d6832a3a59232a64d83d4c0 to c063bf415dac7f7d4df4c37fe76badce76cae3c3.
Expected behavior
install shouldn't change the lock file as there is no reason to change it here (Well it remove the specs: markers but that's not a functional change just a cosmetic one)
Actual behavior
install updates Octokit.fsx to the latest version but not it's Octokit dependency from nuget producing build failures.
If there is a reason that I don't understand for this update to happens, the dependencies should be updated too as in the current state there is no paket update for github dependencies so the only way to update Octokit there is to hand-edit paket.lock.
Known workarounds
Deleting Octokit from paket.lock and re-running an install to get the latest of everything
Pinning the github dependency to a specific version might help
Related information
Tests done on version 3.3.4.0.
PS: Aditionally whatever I do I always have #1750 warning so there's still a bug around this feature :)
The text was updated successfully, but these errors were encountered:
Description
paket installcan change github references inpaket.lockmaking them point to the latest commit.Repro steps
Please provide the steps required to reproduce the problem
build.cmd-> OK.paket\paket.exe installbuild.cmd-> Failurepaket.lock,Octokit.fsxdependency changed fromfsharp/FAKE43c4800c5f132d2c2d6832a3a59232a64d83d4c0toc063bf415dac7f7d4df4c37fe76badce76cae3c3.Expected behavior
installshouldn't change the lock file as there is no reason to change it here (Well it remove thespecs:markers but that's not a functional change just a cosmetic one)Actual behavior
installupdatesOctokit.fsxto the latest version but not it'sOctokitdependency from nuget producing build failures.If there is a reason that I don't understand for this update to happens, the dependencies should be updated too as in the current state there is no
paket updateforgithubdependencies so the only way to updateOctokitthere is to hand-editpaket.lock.Known workarounds
Octokitfrompaket.lockand re-running an install to get the latest of everythingRelated information
Tests done on version 3.3.4.0.
PS: Aditionally whatever I do I always have #1750 warning so there's still a bug around this feature :)
The text was updated successfully, but these errors were encountered: