Repository navigation
chore: pin Rust toolchain to stable with rustfmt, clippy and wasm32v1-none - #261
Nazz-Source wants to merge 1 commit into
Conversation
2fbbe76 to
9653c4b
Compare
|
Warning Possible malicious code: please review before merging. An automated security scan flagged files in this pull request that appear to contain malicious code. Code like this can run automatically when a project is opened in an editor or its dependencies are installed, so it could compromise the machine of anyone who checks out this branch. Automated scans can be wrong, so this may be a false positive. Maintainers: please review the flagged files carefully before merging, on GitHub in your browser rather than by checking out the branch. The malicious part is often hidden far off to the right of an ordinary-looking line, so scroll sideways through each file. @Nazz-Source: this pull request adds or changes these files, possibly without your knowledge. Malware like this spreads by adding itself to repositories on machines it has infected, so your machine might be compromised. Please undo these changes in this pull request, and don't open or run other projects on that machine until you've checked it. Flagged files at commit
Only merge once you're confident these files are safe. ℹ️ Posted automatically by Drips Wave. Questions? Contact support@drips.network. |
Overview
This PR pins the Rust toolchain via
rust-toolchain.tomlso CI no longer floats onstable, which could break the build when a new release introduces new clippy lints. It also documents how to bump the pinned version inCONTRIBUTING.md.Related Issue
Closes #
Changes
🦀 Toolchain Pinning
[ADD]
rust-toolchain.tomlrustfmtandclippycomponents.wasm32v1-nonecompilation target.[MODIFY]
CONTRIBUTING.mdVerification Results
cargo fmt,cargo clippy -- -D warningsandcargo test --workspacepassPROGRESS.mdentry addedCloses #<this issue>Closes #159