libp2p / go-libp2p-kbucket

A kbucket implementation for use as a routing table
MIT License
48 stars 35 forks source link

Bump github.com/libp2p/go-libp2p-peerstore from 0.1.4 to 0.2.0 #56

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps github.com/libp2p/go-libp2p-peerstore from 0.1.4 to 0.2.0.

Release notes

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

v0.2.0

Major features

Peerstore support for certified peer records

Both peerstore implementations (pstoremem and pstoreds) now support certified peer records, by implementing peerstore.CertifiedAddrBook.

For now, the peerstore keeps all addresses, uncertified and certified, and offers no way of differentiating between them when querying it. This means that dials can be insecure (i.e. hitting uncertified addresses when a certified record exists), but it will allow users to being integrating certified records downstream, while we work on tagging addresses properly so they can be subsequently filtered.

The final solution will revolve around address labels, which are being incubated here: libp2p/go-libp2p-core2

Other changes

  • Dependency upgrades.
Commits
  • 59abcf5 Certified addresses (#98)
  • f65b2b4 Merge pull request #124 from jbn/master
  • 4533ab8 Correct path to peer.AddrInfo in deprecation
  • 6c1dc4c Merge pull request #122 from libp2p/dependabot/go_modules/github.com/ipfs/go-...
  • e31ed0a Bump github.com/ipfs/go-datastore from 0.4.2 to 0.4.4
  • 38d6b3c Merge pull request #121 from libp2p/chore/update-ds
  • b4dc608 chore(dep): update go-log
  • 0f8a83b Merge pull request #120 from libp2p/dependabot/go_modules/github.com/ipfs/go-...
  • 4f2f613 Bump github.com/ipfs/go-datastore from 0.4.1 to 0.4.2
  • d6f697f Merge pull request #119 from libp2p/dependabot/go_modules/github.com/ipfs/go-...
  • 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)