berty / go-libp2p-tor-transport

🚧 WIP: tor transport for libp2p
Apache License 2.0
53 stars 7 forks source link

fix(deps): bump github.com/libp2p/go-libp2p-core from 0.8.0 to 0.13.0 #98

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps github.com/libp2p/go-libp2p-core from 0.8.0 to 0.13.0.

Release notes

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

v0.13.0

What's Changed

Full Changelog: https://github.com/libp2p/go-libp2p-core/compare/v0.12.0...v0.13.0

v0.12.0

What's Changed

New Contributors

Full Changelog: https://github.com/libp2p/go-libp2p-core/compare/v0.11.0...v0.12.0

v0.11.0

This release removes the ConnHandler interface, both its definition, as well as its use in the Network interface.

v0.10.0

This release contains a number of backwards-incompatible changes:

  • replaces the Process method on the Network interface with an io.Closer (#212)
  • adds the role (client / server) to the simultaneous connect context (#210)
  • passes the peer ID to SecureInbound in the SecureTransport and the SecureMuxer (#211)

v0.9.0

In this release, we removed a number functions and types that have long been deprecated:

  • crypto/KeyStretcher and crypto.StretchedKeys (#203)
  • Bytes method from the crypto.Key interface (#204)
  • peer.IDB58Decode, peer.IDB58Encode, peer.IdHexDecode, peer.IdHexEncode (#205)
  • insecure.New constructor for the insecure transport (#206)

v0.8.6

No release notes provided.

v0.8.5

Introduces a context option to signify simultaneous connect for hole punching.

v0.8.4

Introduces an Event to detect TCP & UDP NAT Device Type.

v0.8.3

Adds support for forcing a direct connection with a peer even if we already have a relayed connection.

v0.8.2

  • #175 -- Adds support for transient connections.

v0.8.1

  • Introduce a sec.SecureMuxer interface which can select security protocols and open outbound connections with simultaneous open. It is a wrapper around the SecureTransport interface.
Commits


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[bot] commented 2 years ago

Superseded by #101.