feat(deps): update to graphsync v0.13.0 with 2.0 protocol #8273
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.
Proposed Changes
This PR updates go-graphsync and go-data-transfer. From the standpoint of Lotus, it's very small. However, the 0.13.0 version of go-graphsync includes significant changes. You can see them in go-graphsync's CHANGELOG here: https://github.com/ipfs/go-graphsync/blob/main/CHANGELOG.md
The only changes in Lotus other than go.mod updates are that GraphSync has a new ID type for Requests -- they are now UUIDs. I made a small change to the MinerTransferDiagnostics API, which I'm pretty sure no one but me knows about or uses anyway :)
Additional Info
Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>
fix: mempool: Introduce a cache for valid signatures
PR type
: fix, feat, INTERFACE BREAKING CHANGE, CONSENSUS BREAKING, build, chore, ci, docs,perf, refactor, revert, style, testarea
: api, chain, state, vm, data transfer, market, mempool, message, block production, multisig, networking, paychan, proving, sealing, wallet, deps