Bump kubo-rpc-client v3 to v4 #152
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cedric25
added a commit
that referenced
this pull request
Aug 8, 2024
* update deps * add AbstractProvider and AbstractSigner support in constructor * update changelog * fix possible race condition in subgraph indexation * Bump kubo-rpc-client v3 to v4 (#152) * Add `kubo-rpc-client` bump to changelog * 1.0.4 * Fix changelog? --------- Co-authored-by: Pierre Jeanjacquot <26487010+PierreJeanjacquot@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why?
PR on kubo's side: ipfs/js-kubo-rpc-client#221
Especially:
Which does some magic trying to find the correct
fetchimplementation, which seems to break usage of our SDK in Next.js SSR.Same PR for
dataprotector-sdk: iExecBlockchainComputing/dataprotector-sdk#341