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
bat cannot be built with Rust 1.40 without passing the --locked flag. This is because the semver dependency has semver-parser as a dependency and this crate started using a new feature in a minor version patch (v0.10.1) that is available only from Rust 1.44 onwards. The lockfile on the master branch has semvar-parser locked at v0.10.0 which still compiles. To reproduce, run
$ rm Cargo.lock
$ rustup default 1.40
$ cargo b
To eliminate this issue, the version of the sub dependency can be held in place as done here or the MSRV of bat could be lifted to 1.44.
I encountered this problem first in this PR where I added a new dependency and wanted to ship a fresh lockfile with the addition, but the MSRV CI runner failed due to this.
This is all assuming you see this as an issue in the first place, after all the build instructions tell you to use the --locked flag, as sharkdp pointed out under the aforementioned PR.
The text was updated successfully, but these errors were encountered:
bat
cannot be built with Rust 1.40 without passing the--locked
flag. This is because thesemver
dependency hassemver-parser
as a dependency and this crate started using a new feature in a minor version patch (v0.10.1) that is available only from Rust 1.44 onwards. The lockfile on the master branch hassemvar-parser
locked at v0.10.0 which still compiles. To reproduce, runTo eliminate this issue, the version of the sub dependency can be held in place as done here or the MSRV of
bat
could be lifted to 1.44.I encountered this problem first in this PR where I added a new dependency and wanted to ship a fresh lockfile with the addition, but the MSRV CI runner failed due to this.
This is all assuming you see this as an issue in the first place, after all the build instructions tell you to use the
--locked
flag, as sharkdp pointed out under the aforementioned PR.The text was updated successfully, but these errors were encountered: