I hate to do this a bit, but I think it's best for the community in the longer run (though maybe not for our short-term release reputation ๐คจ ๐) to do another turn here and go back up again to BN.jsv5 now with the interoperability patches out.
This will ensure that the libraries will slowly get up to the latest version and will further profit from patches and upgrades (which will likely get published on the latest v5 branch).
Coverage remained the same at 99.705% when pulling 37c3727cddfe02554620788849b4b7f1ec7bdefc on new-release into 806b2b200d9ae7f7bbcd0b53d5397c3d737e5a75 on master.
I hate to do this a bit, but I think it's best for the community in the longer run (though maybe not for our short-term release reputation ๐คจ ๐) to do another turn here and go back up again to
BN.js
v5
now with the interoperability patches out.This will ensure that the libraries will slowly get up to the latest version and will further profit from patches and upgrades (which will likely get published on the latest
v5
branch).