nushell/rust-toolchain.toml

# 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"
# 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
# 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.
channel = "1.70.0"
add rust toolchain file to pin rust version (#6298) * add rust toolchain file to pin rust version * rust 1.63 release, bump toolchain * linux clippy * pin to 1.63 * pin to 1.61 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"`
with the release of rust 1.67, let's bump to 1.66.1 (#7866) # Description This PR bumps the required rust version to 1.66.1. # User-Facing Changes # Tests + Formatting Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass # After Submitting If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. 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`
add rust toolchain file to pin rust version (#6298) * add rust toolchain file to pin rust version * rust 1.63 release, bump toolchain * linux clippy * pin to 1.63 * pin to 1.61 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.`
bump rust-toolchain to 1.70.0 (#10113) # Description This PR bumps the rust-toolchain to 1.70.0 since 1.72.0 was released today. # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass (on Windows make sure to [enable developer mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging)) - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > Note > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. --> 2023-08-25 02:13:57 +02:00			`channel = "1.70.0"`