Version 0.25.0

New

• [improved] sendMessage now returns the messageProcessingState - structure that includes the last shard block that was created before the message was sent. Specify this block in the new waitForDeployTransaction/waitForTransaction method and wait for the transaction starting from it.
• [new] waitForDeployTransaction/waitForRunTransaction methods. Wait for the transaction of a previously sent message using new mechanism of sequential shard block reading. In case of network problems (e.g. if some shard start lagging) returns the updated message processing state with the last checked block. Use it to resume waiting later.
• [improved] processMessage now takes new infiniteWait parameter - it allows to infinitely wait for the transaction even if there are some network problems (like shard lags). If set to false - also returns updated messageProcessingState in case of network problems
• TONContractMessage includes the address field (equals to the dst)
• Support for core contexts.
• Test suite have been refactored and can be easily adopted to run on several JS targets.
• networkTimeout configuration parameter added for retrying GraphQL requests in case of network errors. Default value is 0 which means infinite retries until the network connection will be succeeded.
• New message processing tracing. Client starts root processing span with traceId and spanId calculated from messageId. Other components can report child span without passing parent context through pipeline.
• messageProcessingTimeoutGrowFactor field removed from config since it's not used
• graphql queries can be forcible aborted on a timeout in case of a half-open TCP connection,