2022-08-11 22:45:01 +02:00
|
|
|
# So, you want to update the Rust toolchain...
|
|
|
|
|
# The key is making sure all our dependencies support the version of Rust we're using,
|
|
|
|
|
# and that nushell compiles on all the platforms tested in our CI.
|
|
|
|
|
|
|
|
|
|
# Here's some documentation on how to use this file:
|
|
|
|
|
# https://rust-lang.github.io/rustup/overrides.html#the-toolchain-file
|
|
|
|
|
|
|
|
|
|
[toolchain]
|
|
|
|
|
# The default profile includes rustc, rust-std, cargo, rust-docs, rustfmt and clippy.
|
|
|
|
|
# https://rust-lang.github.io/rustup/concepts/profiles.html
|
|
|
|
|
profile = "default"
|
2023-01-26 22:31:17 +01:00
|
|
|
# The current plan is to be 1 release behind the latest stable release. So, if the
|
|
|
|
|
# latest stable release is 1.62.0, the channel should be 1.61.0. We want to do this
|
2022-08-11 22:45:01 +02:00
|
|
|
# so that we give repo maintainers and package managers a chance to update to a more
|
|
|
|
|
# recent version of rust. However, if there is a "cool new feature" that we want to
|
|
|
|
|
# use in nushell, we may opt to use the bleeding edge stable version of rust.
|
|
|
|
|
# I believe rust is on a 6 week release cycle and nushell is on a 3 week release cycle.
|
|
|
|
|
# So, every two nushell releases, this version number should be bumped by one.
|
2023-01-26 22:31:17 +01:00
|
|
|
channel = "1.66.1"
|
|
|
|
|
|
