Bump libp2p-identity from 0.2.7 to 0.2.8

[dependabot]

Bumps libp2p-identity from 0.2.7 to 0.2.8.

Release notes

Sourced from libp2p-identity's releases.

libp2p-v0.53.1

See individual changelogs for details.

libp2p-v0.53.0

The most ergonomic version of rust-libp2p yet!

We've been busy again, with over 250 PRs being merged into master since v0.52.0 (excluding dependency updates).

Backwards-compatible features

Numerous improvements landed as patch releases since the v0.52.0 release, for example a new, type-safe SwarmBuilder that also encompasses the most common transport protocols:

let mut swarm = libp2p::SwarmBuilder::with_new_identity()
    .with_tokio()
    .with_tcp(
        tcp::Config::default().port_reuse(true).nodelay(true),
        noise::Config::new,
        yamux::Config::default,
    )?
    .with_quic()
    .with_dns()?
    .with_relay_client(noise::Config::new, yamux::Config::default)?
    .with_behaviour(|keypair, relay_client| Behaviour {
        relay_client,
        ping: ping::Behaviour::default(),
        dcutr: dcutr::Behaviour::new(keypair.public().to_peer_id()),
    })?
    .build();

The new builder makes heavy use of the type-system to guide you towards a correct composition of all transports. For example, it is important to compose the DNS transport as a wrapper around all other transports but before the relay transport. Luckily, you no longer need to worry about these details as the builder takes care of that for you! Have a look yourself if you dare here but be warned, the internals are a bit wild :)

Some more features that we were able to ship in v0.52.X patch-releases include:

• stable QUIC implementation
• for rust-libp2p compiled to WASM running in the browser
  • WebTransport support
  • WebRTC support
• UPnP implementation to automatically configure port-forwarding with ones gateway
• option to limit connections based on available memory

We always try to ship as many features as possible in a backwards-compatible way to get them to you faster. Often times, these come with deprecations to give you a heads-up about what will change in a future version. We advise updating to each intermediate version rather than skipping directly to the most recent one, to avoid missing any crucial deprecation warnings. We highly recommend you stay up-to-date with the latest version to make upgrades as smooth as possible.

Some improvments we unfortunately cannot ship in a way that Rust considers a non-breaking change but with every release, we attempt to smoothen the way for future upgrades.

#[non_exhaustive] on key enums

We've identified that adding a new "message" to the ToSwarm enum is a common cause for breaking changes. This enum is used by plugins (i.e. NetworkBehaviours) to communicate with the Swarm. Similarly, the FromSwarm enum is used to inform plugins about state changes. By adding #[non_exhaustive] to these and other enums we enable future additions to be non-breaking changes.

... (truncated)

Commits

• 7d982f7 deps(identity): bump ring to v0.17.5
• 9fed1a9 fix(chat-example): set idle_connection_timeout
• 51832fb fix(dns): bump version
• 7f4ba69 chore: prepare v0.53.1
• 3ec575a feat(quic): allow disabling of path MTU discovery
• 441c242 feat(libp2p): track bandwidth per transport protocol stack
• 9ab0e6f feat(libp2p): add SwarmBuilder::with_dns_config
• 2b12663 fix(kad): potentially incorrect return value of Addresses::remove
• 2fb671c feat(kad): impl Display on QueryId
• 2ecc7cf fix: Add SwarmBuilder::with_quic_config for TcpPhase
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)