had tried bump neon and neon-build in Cargo.toml to 0.9.1 successfully builded on 18.x, ubuntu-latest ✅ here
18.x, macos-latest failed when try to Compiling crossbeam-channel v0.5.5 here
locally with M2 running yarn install && yarn build
neon 0.9.1 failed around Compiling bbs v0.4.1
neon 0.10.1 failed around Compiling node-bbs-signatures v0.1.0
[ ] Tests for the changes have been added (for bug fixes / features)
Description
had tried bump neon and neon-build in Cargo.toml to 0.9.1 successfully builded on 18.x, ubuntu-latest ✅ here 18.x, macos-latest failed when try to Compiling crossbeam-channel v0.5.5 here locally with M2 running yarn install && yarn build neon 0.9.1 failed around Compiling bbs v0.4.1 neon 0.10.1 failed around Compiling node-bbs-signatures v0.1.0
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] The commit message(s) follow conventional commits
[ ] Documentation has been added / updated (for bug fixes / features)
[ ] Changes follow the contributing document.
Motivation and Context
Does this PR introduce a breaking change?
Which merge strategy will you use?