crate compile warnings treated as errors

[mcandre]

Unlike on my local (macOS) machine, the same cargo install --force cross --git https://github.com/cross-rs/cross --rev 4e64366af6095c84fa4f54a0fa5a2ba7d9a271aa command with setup-rust-toolchain in GitHub Actions somehow treats crate warnings as errors.

This causes my jobs to fail when updating to Rust 1.86.0.

https://github.com/mcandre/crit/actions/runs/14273528463/job/40011901318

See also cross-rs/cross#1662

[Emilgardis]

This is expected default behaviour. You can unset the RUSTFLAGS env set by the action with the rustflags input

also #48

[jonasbb]

This is an unwanted side effect of setting the RUSTFLAGS environment variable. You find the reasoning better explained in #48. You can provide your own rustflags input or unset the RUSTFLAGS variable for the cargo install step.