mirror of
https://github.com/nushell/nushell
synced 2024-12-26 13:03:07 +00:00
1d418030e1
# Description With the release of Rust 1.77.0 today we're able to bump the rust-toolchain for nushell to 1.75.0. # 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. -->
19 lines
1.1 KiB
TOML
19 lines
1.1 KiB
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 2 releases behind the latest stable release. So, if the
|
|
# latest stable release is 1.72.0, the channel should be 1.70.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 4 week release cycle.
|
|
# So, every two nushell releases, this version number should be bumped by one.
|
|
channel = "1.75.0"
|