In japaric/xargo#264 I am trying to ensure that xargo's lockfile is up-to-date on CI, so I added --locked to our cross build invocation. However, that seems to have no effect: even with a stale lockfile, and even with no lockfile at all, the build succeeds!

Silently ignoring important CLI flags like that seems quite surprising, so I was wondering if this is deliberate and if there's any way to do a locked build here.