Paket: Why doesn't restore fail on out of sync?

[sarudak]

When I run paket restore after a change to the paket.dependencies file I get 'paket.dependencies and paket.lock are out of sync' and it suggests I do an install or update. However the packet restore proceeds normally and does not fail. Is there a reason it behaves like this? It seems failure would be the desired behavior unless you specified otherwise however there's no option to force a failure when the lock file is out of sync. This is problematic for us because it allows forgetful developers to commit mismatched files that don't fail locally and don't fail the build but don't necessarily have the expected behavior.

[forki]

This is by design. We always restore exactly the stuff that's given in the lock file.

[forki]

That said, I think a special command line parameter that fails the build in such a situation would be accepted.

[sarudak]

https://github.com/fsprojects/Paket/pull/1963

[sarudak]

I seem to be having integration tests failing on linux but not on windows and I haven't been able to replicate locally.

[enricosada]

Closing, added by @sarudak as --fail-on-checks