Forced update resets gist dependency

[tpluscode]

When there is a gist dependency locked to some commit other than the initial running paket.exe update --force downloads the gist's first commit and updates paket.lock accordingly. Can be reproduced in this repo

[forki]

strange I get the following expected diff:

[tpluscode]

That's it precisely what I meany though it seem that I wrongly assumed 5d9 was the initial commit. It's even worse because it's the gist id only. I though they were the same thing. And 77ad6 is the latest revision, which should appear in paket.lock after running update, forced or otherwise.

[forki]

Look into your dependencies file. You pinned the commit to 5d9 - I think it's all correct now.

[tpluscode]

Why do say I pinned the commit? Looks fine to me

[forki]

sorry my bad. that hash is not the version but the gist identifier.

will try to fix asap.