I updated the actions/upload-artifacts and actions/download-artifacts and the API changed slightly so it didn't work the way it used to in the old workflow.
There were a couple of other small things that I noticed during publishing
tested the package that gets published and needed to add types back in to get working in @chainsafe/bls
remove @jazzer.js/core from optionalDependencies to stop it from getting installed by dependent packages
add @jazzer.js/core in fuzz test on the fly on first run
there is a 1 in 100 fail on unit test. the error message returned from supranational/blst changes in rare instances. There is still an error thrown, its just the error message that gets check by unit test changes from BLST_POINT_NOT_ON_CURVE to BLST_BAD_ENCODING
Description
I updated the actions/upload-artifacts and actions/download-artifacts and the API changed slightly so it didn't work the way it used to in the old workflow.
There were a couple of other small things that I noticed during publishing
@chainsafe/bls
@jazzer.js/core
from optionalDependencies to stop it from getting installed by dependent packages@jazzer.js/core
in fuzz test on the fly on first runBLST_POINT_NOT_ON_CURVE
toBLST_BAD_ENCODING