libp2p / go-libp2p-examples

Example libp2p applications
MIT License
339 stars 145 forks source link

Bump github.com/libp2p/go-libp2p-kad-dht from 0.4.1 to 0.5.0 #109

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps github.com/libp2p/go-libp2p-kad-dht from 0.4.1 to 0.5.0.

Release notes

Sourced from github.com/libp2p/go-libp2p-kad-dht's releases.

v0.5.0

Switch to using multihashes in provider records. When providing a CID, we now strip the codec/version and provide the raw multihash. When searching for a CID, we do the same.

  • For CIDv0, this changes nothing. CIDv0 CIDs are just raw multihashes.
  • For CIDv1, new nodes and old nodes will not find each other. Given the current state of content routing and the fact that most files use CIDv0, this shouldn't cause too many issues (and it's better to do this before we fix the DHT).

This release also updates the bootstrap list to remove the bootstrappers with 1024 bit keys.

Finally, this improves the bucket refreshing logic to ensure we better connect to nodes close to us in the DHT.

Commits
  • 95964c0 Merge pull request #422 from libp2p/feat/advertise-multihash
  • 6c4cd42 Merge pull request #433 from aarshkshah1992/fix/flaky-TestEmptyTable-test
  • b19ac72 routing table should not have all the peers
  • 5d2e3df make all key types loggable
  • 3e24f35 provider record keys can be an arbitrary byte array less than 80 bytes instea...
  • a4b38ee feat(dht): provider records use multihashes instead of CIDs
  • a06b327 Merge pull request #432 from libp2p/dependabot/go_modules/github.com/libp2p/g...
  • 23e3b62 build(deps): bump github.com/libp2p/go-libp2p from 0.4.2 to 0.5.0
  • 4e19da1 Merge pull request #430 from libp2p/feat/update-bootstrappers
  • 9c060c8 chore(bootstrap): update bootstrappers
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)