-
Notifications
You must be signed in to change notification settings - Fork 313
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
pin the toolchain version used by clippy #846
Conversation
I was working on this but was kinda blocked (I mostly discover dependabot to be honest), so thanks. What bug me about this kind of change is #758 that we did not want. Are you saying that |
You certainly can configure dependabot to ignore the whole action, but that would also prevent it from bumping the pinned clippy toolchain version. Dependabot doesn't parse the toolchain config, only the action version, so this should work fine (though it's untested). I can probably test it on a fork to confirm it works the way I expect |
Ok that seems good. Another thing that bothered me in #758 was that it suggested to update the version to "1.80.0" while I thought it would have suggested "1.74.0" (or whatever appropriate version at the time it wrote it). |
I missed that, that could be a problem. |
This is intentional but it's convenient ahead-of-time PR. |
For my taste, this is too many things in one PR. |
pinning the version of linters is a general pattern, not limited to the Rust ecosystem |
- uses: dtolnay/rust-toolchain@master
with:
toolchain: stable
components: rustfmt to - uses: dtolnay/rust-toolchain@stable
with:
components: rustfmt is not strictly required, but trivial. All other changes are required. |
i think this might be deal-breaker unfortunately |
I agree. I think we are gonna stick with stable clippy and handle rare breakage as soon as it appears. PS: There is not that many things in that PR. |
Thank you anyway. |
see discussion in #618