Pin Rust version #247
Labels
exp: low
Achievable with little prior knowledge and guidance
good first issue
Good for newcomers
pri: low
An issue with no impact to quality, performance, or functionality
type: build
Changes that affect the build system or external dependencies
Milestone
Everytime Rust releases a new version our builds break. This happens because new lints are added for instance. We want to keep up to date with the latest Rust version but its anoying that if someone submits a PR CI might fail because a new Rust version was just released.
I propose we do something similar to
vector
, they store a file that stores which version of Rust CI should use. Its trivial to bump Mun to a new Rust version by creating a new PR that modifies the contents of that file together with fixing any issues that may be caused by the version bump.To implement this we just need to modify our CI workflow to read the version to use from a file.
Good first issue process:
If this is your first PR, welcome 🎉 😄
The text was updated successfully, but these errors were encountered: