Pin nightly to 2024-05-04 due to recently-enabled check-cfg

[ryoqun]

I'm jumping on this workaround in #1040 (comment) in desperation of shipping select_biased!, assuming build.rs isn't a viable option (as concerns is raised upstream: rust-lang/rust#124800)....:

Maybe pinning to older nightly (nightly-2024-05-04 or earlier according to https://blog.rust-lang.org/2024/05/06/check-cfg.html) in crossbeam CI isn't a viable option?

[ryoqun]

@taiki-e could you review this?

fyi, you can see ci builds as if these changes were on the master branch here: https://github.com/ryoqun/crossbeam/actions/runs/9089208830 (That's why I'm creating this pr from my fork's master branch). it seems that cirrus ci isn't run there understandably..

[taiki-e]

Thanks for the PR! I would like to use rust-lang/cargo#13913 's config option instead if possible.

[ryoqun]

Thanks for the PR! I would like to use rust-lang/cargo#13913 's config option instead if possible.

@taiki-e seems rust-lang/cargo#13913 is synced to the rustc repo and nightly-2024-05-19 contains it. Although, the diagnostics aren't updated yet (rust-lang/rust#125219), I'll soon open another pr. so closing this now.