8 comments
@predrag at work we just pin the rust version and update it with a job. If the update job fails we fix in the same change and submit together. @epage yeah. We do the same thing at work, which is the CI thing that breaks (not mainline). I want to adapt it to try running with `—fix` and then updating the change, but haven’t got there yet. But then there are some OSS projects I contribute to that just pull the latest version in on PR checks. I’ve found out about a Rust update in minutes after the release more than once because of that. Should probably try to convince someone to go the pinned rust route there too. @hds If people need an example of this, see https://github.com/epage/_rust That is the template for all my projects. |
@hds this is why I recommend a once-a-month job that compiles + runs clippy on your project using beta Rust.
If it triggers new lints and fails, you have an entire month to fix it before it breaks your PR's CI flow 🦀