This is odd, CI should have failed because the lockfile actually isn't up-to-date...

Are you sure --locked works properly when the only changes are not related to dependencies? There's also --frozen but I never know the difference.

A cargo build --locked locally failed when I prepared this PR.

But maybe cross breaks --locked?

Turns out that yes, this is a cross issue and they are working on it.

Meanwhile, no reason not to land this here so that we get the fix once cross is fixed -- @jethrogb what do you think?

There's also --frozen but I never know the difference.

--frozen implies --locked, but also refuses to download new crates into cargo's cache (it's basically "offline mode").

The cross issue is fixed; I will land this here.

bors r+

Build succeeded

• continuous-integration/travis-ci/push