hi @Goodness,
the issue here is that from the api freeze of the node to the deployment (tomorrow is HF for testnet) there wasn’t enough time to catch up and make a release update with the support for the new node.
Also today there was a last minute change on the node that will affect the release schedule of the SDKs and the aepps that use it.
It will take a little bit more to stabilise the project, but the people are working on there should be soon updates