-
Notifications
You must be signed in to change notification settings - Fork 1.1k
chore: Add rust-toolchain.toml to ensure consistent toolchain version #7972
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
THANK YOU @EricccTaiwan -- this is super helpful |
rust-toolchain.toml
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think of adding a specific release here like https://github.com/apache/datafusion/blob/70e7eb3aaef221c8fefe2eee6198e9a61d68bc0f/rust-toolchain.toml#L22
1.88
That will prevent random failure when new stable releases are released
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think of adding a specific release here like https://github.com/apache/datafusion/blob/70e7eb3aaef221c8fefe2eee6198e9a61d68bc0f/rust-toolchain.toml#L22
1.88That will prevent random failure when new stable releases are released
Makes sense. Using 1.88 avoids random breakage, though it means running rustup manually.
I'm okay with both. What do you prefer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is preferable to have to manually bump it to avoid CI randomly breaking when a new rust version is released.
- For example Fix clippy for Rust 1.88 release #7797
|
By the way, would it make sense to also add |
6173a17 to
82c42da
Compare
I am not sure |
alamb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @EricccTaiwan -- think this looks great to me
Just thought it might be helpful for consistency, and possibly more contributor-friendly too -- especially for folks who rely on |
|
Hmm, looks like the CI jobs will need to be updated to account for the new toolchain somehow |
Yes, I see -- I can give it a try to modify the CI part. |
I think can make (another) PR into your own fork to test the CI |
This file ensures that contributors and CI use the same Rust toolchain, preventing version mismatch issues and improving reproducibility. Signed-off-by: Cheng-Yang Chou <[email protected]>
82c42da to
f782ef9
Compare
I'm a bit confused — on my fork, CI only seems to run on the main branch. When I sync with upstream, it works fine, but creating a new branch (like this PR) doesn’t trigger CI at all. Edit: Cuz I need CI to show me what needs changing. 😢 |
CI jobs on this (the upstream) repo need approval for first time contributors. Once we have merged a PR from you then the CI starts automatically on subsequent PRs |
|
Here is an example of what happens without this PR:
|
|
Since the new upgrade just caused me annoyance I am going to try and push this PR through (It will be easier for me as I can trigger CI). Thanks you @EricccTaiwan |
Hi @alamb , I’ve been a bit busy lately, and this change looks a bit more involved than I can tackle right now. |
No worries -- thank you for the help. I will get this one over the line. Than you for all your help so far |
|
|
||
| name: Prepare Rust Builder | ||
| description: 'Prepare Rust Build Environment' | ||
| inputs: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed these parameters as almost all uses installed stable
| target: wasm32-unknown-unknown,wasm32-wasip1 | ||
| - name: Install wasm32 targets | ||
| run: | | ||
| rustup target add wasm32-unknown-unknown |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| docs: | ||
| name: Rustdocs are clean | ||
| runs-on: ubuntu-latest | ||
| strategy: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is let over from a previous time when we checked docs on different configurations -- at the moment there is a single pair that is used, so I unparameterized this and made the version used explicit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
Thanks again @EricccTaiwan -- since there has been no more comments on this PR I will merge it in |
Thanks @alamb, for doing most of the work, lol! |


Which issue does this PR close?
None.
Rationale for this change
Without a fixed toolchain, contributors may use different Rust versions, leading to inconsistent Clippy lints or build errors (e.g., from renamed lints). This change ensures that the project builds consistently across environments.
What changes are included in this PR?
rust-toolchain.tomlfile to pin the Rust toolchain to thestablechannel.Are these changes tested?
This change affects toolchain configuration and does not modify runtime code. Behavior is implicitly tested via CI builds, which will now consistently use the pinned toolchain.
Are there any user-facing changes?
No.