derive macro warning: unexpected `cfg` condition name: `wasm_bindgen_unstable_test_coverage`

[mirsella]

version: wasm-bindgen v0.2.95
Recent rust nightly version enabled by default the unexpected_cfgs, which lead to this warning:

warning: unexpected `cfg` condition name: `wasm_bindgen_unstable_test_coverage`
  --> game/src/lib.rs:29:1
   |
29 | #[wasm_bindgen]
   | ^^^^^^^^^^^^^^^
   |
   = help: consider using a Cargo feature instead
   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
            [lints.rust]
            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(wasm_bindgen_unstable_test_coverage)'] }
   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(wasm_bindgen_unstable_test_coverage)");` to the top of the `build.rs`
   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
   = note: this warning originates in the attribute macro `wasm_bindgen` (in Nightly builds, run with -Z macro-backtrace for more info)

[bcheidemann]

For anyone else coming across this, you can statically declare the cfg as expected by adding the following to your Cargo.toml:

[lints.rust]
unexpected_cfgs = { level = "warn", check-cfg = ['cfg(wasm_bindgen_unstable_test_coverage)'] }

[daxpedda]

Fixed by #4284.

[mirsella]

nice, that's a better fix than just ignoring the lint

[mirsella]

since this can break CI by emitting a warning to potentially a lot of people, it would be nice to have a patch release
thanks and have a good day :)

[daxpedda]

since this can break CI by emitting a warning to potentially a lot of people, it would be nice to have a patch release thanks and have a good day :)

I plan to make one today or at the latest tomorrow.