fluencelabs/rust-libp2p
1
0
Fork 0
mirror of https://github.com/fluencelabs/rust-libp2p synced 2025-05-23 16:11:19 +00:00
Code Issues Projects Releases Wiki Activity
rust-libp2p/core/CHANGELOG.md

444 lines
17 KiB
Markdown
Raw Normal View History

refactor!: Move `ConnectionId` and `PendingPoint` to `libp2p-swarm` (#3346) Both of these are only needed as part of `libp2p-swarm`. Them residing in `libp2p-core` is a left-over from when `libp2p-core` still contained `Pool`.
2023-01-18 19:56:32 +11:00
# 0.39.0 [unreleased]
- Move `ConnectionId` to `libp2p-swarm`. See [PR 3221].
- Move `PendingPoint` to `libp2p-swarm` and make it crate-private. See [PR 3221].
[PR 3221]: https://github.com/libp2p/rust-libp2p/pull/3221
chore: Prepare rust-libp2p v0.50.0 release (#3163)
2022-11-25 10:37:55 +01:00
# 0.38.0
*: Don't leak `prost` dependency in error types (#3058) With the current design, a major version bump of `prost` leaks into all consumers of `prost-codec`.
2022-11-02 23:02:21 +11:00
core/muxer: Remove deprecated functions (#3031)
2022-11-03 02:09:12 +11:00
- Remove deprecated functions `StreamMuxerExt::next_{inbound,outbound}`. See [PR 3031].
*: Don't leak `prost` dependency in error types (#3058) With the current design, a major version bump of `prost` leaks into all consumers of `prost-codec`.
2022-11-02 23:02:21 +11:00
- Hide `prost::Error` from public API in `FromEnvelopeError::InvalidPeerRecord` and `signed_envelope::DecodingError`. See [PR 3058].
feat(swarm): Make executor for connection tasks explicit (#3097) Previously, the executor for connection tasks silently defaulted to a `futures::executor::ThreadPool`. This causes issues such as https://github.com/libp2p/rust-libp2p/issues/2230. With this patch, we force the user to choose, which executor they want to run the connection tasks on which results in overall simpler API with less footguns. Closes #3068.
2022-11-15 15:26:03 +01:00
- Move `Executor` to `libp2p-swarm`. See [PR 3097].
.github/workflows: Refactor CI jobs (#3090) We refactor our continuous integration workflow with the following goals in mind: - Run as few jobs as possible - Have the jobs finish as fast as possible - Have the jobs redo as little work as possible There are only so many jobs that GitHub Actions will run in parallel. Thus, it makes sense to not create massive matrices but instead group things together meaningfully. The new `test` job will: - Run once for each crate - Ensure that the crate compiles on its specified MSRV - Ensure that the tests pass - Ensure that there are no semver violations This is an improvement to before because we are running all of these in parallel which speeds up execution and highlights more errors at once. Previously, tests run later in the pipeline would not get run at all until you make sure the "first" one passes. We also previously did not verify the MSRV of each crate, making the setting in the `Cargo.toml` rather pointless. The new `cross` job supersedes the existing `wasm` job. This is an improvement because we now also compile the crate for windows and MacOS. Something that wasn't checked before. We assume that checking MSRV and the tests under Linux is good enough. Hence, this job only checks for compile-errors. The new `feature_matrix` ensures we compile correctly with certain feature combinations. `libp2p` exposes a fair few feature-flags. Some of the combinations are worth checking independently. For the moment, this concerns only the executor related transports together with the executor flags but this list can easily be extended. The new `clippy` job runs for `stable` and `beta` rust. Clippy gets continuously extended with new lints. Up until now, we would only learn about those as soon as a new version of Rust is released and CI would run the new lints. This leads to unrelated failures in CI. Running clippy on with `beta` Rust gives us a heads-up of 6 weeks before these lints land on stable. Fixes #2951.
2022-11-18 22:04:16 +11:00
- Update `rust-version` to reflect the actual MSRV: 1.60.0. See [PR 3090].
- Update `multistream-select` to `v0.12.1`. See [PR 3090].
feat: Better error reporting when features are disabled (#2972) In case support for e.g. RSA keys is disabled at compile-time, we will now print a better error message. For example: > Failed to dial Some(PeerId("QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt")): Failed to negotiate transport protocol(s): [(/dnsaddr/bootstrap.libp2p.io/p2p/QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt): : Handshake failed: Handshake failed: Invalid public key: Key decoding error: RSA keys are unsupported)] Fixes #2971.
2022-11-23 11:51:47 +11:00
- Improve error messages in case keys cannot be decoded because of missing feature flags. See [PR 2972].
refactor(core)!: remove `EitherError` in favor of `either::Either` (#3337) Defining our own `EitherError` type has no value now that `Either` provides the same implementation. Related: https://github.com/libp2p/rust-libp2p/issues/3271
2023-01-18 10:05:59 +11:00
- Remove `EitherError` in favor of `either::Either`. See [PR 3337].
refactor(core)!: remove `EitherTransport` (#3338) We don't need to define our own type here, we can simply implement `Transport` on `either::Either`.
2023-01-18 11:58:09 +11:00
- Remove `EitherTransport` in favor of implementing `Transport` on `either::Either`. See [PR 3338].
refactor(core)!: remove `EitherUpgrade` (#3339) We don't need to define our own type here, we can simply implement `UpgradeInfo`, `InboundUpgrade` and `OutboundUpgrade` on `either::Either`.
2023-01-18 13:35:07 +11:00
- Remove `EitherUpgrade` in favor of implementing `UpgradeInfo`, `InboundUpgrade` and `OutboundUpgrade` on `either::Either`. See [PR 3339].
refactor(core)!: remove `EitherFuture2` (#3340) We can completely replace `EitherFuture2` with `EitherFuture`. `EitherFuture` itself cannot be removed for now because the `Future` implementation on `future::Either` forces both `Future`s to evaluate to the same type.
2023-01-18 21:17:18 +11:00
- Remove `EitherFuture2` in favor of `EitherFuture`. See [PR 3340].
refactor(core)!: remove `EitherOutput` (#3341) The trick with this one is to use `futures::Either` everywhere where we may wrap something that implements any of the `futures` traits. This includes the output of `EitherFuture` itself. We also need to implement `StreamMuxer` on `future::Either` because `StreamMuxer`s may be the the `Output` of `InboundUpgrade`.
2023-01-23 23:31:30 +11:00
- Remove `EitherOutput` in favor of `future::Either`. See [PR 3341].
core/muxer: Remove deprecated functions (#3031)
2022-11-03 02:09:12 +11:00
[PR 3031]: https://github.com/libp2p/rust-libp2p/pull/3031
*: Don't leak `prost` dependency in error types (#3058) With the current design, a major version bump of `prost` leaks into all consumers of `prost-codec`.
2022-11-02 23:02:21 +11:00
[PR 3058]: https://github.com/libp2p/rust-libp2p/pull/3058
feat(swarm): Make executor for connection tasks explicit (#3097) Previously, the executor for connection tasks silently defaulted to a `futures::executor::ThreadPool`. This causes issues such as https://github.com/libp2p/rust-libp2p/issues/2230. With this patch, we force the user to choose, which executor they want to run the connection tasks on which results in overall simpler API with less footguns. Closes #3068.
2022-11-15 15:26:03 +01:00
[PR 3097]: https://github.com/libp2p/rust-libp2p/pull/3097
.github/workflows: Refactor CI jobs (#3090) We refactor our continuous integration workflow with the following goals in mind: - Run as few jobs as possible - Have the jobs finish as fast as possible - Have the jobs redo as little work as possible There are only so many jobs that GitHub Actions will run in parallel. Thus, it makes sense to not create massive matrices but instead group things together meaningfully. The new `test` job will: - Run once for each crate - Ensure that the crate compiles on its specified MSRV - Ensure that the tests pass - Ensure that there are no semver violations This is an improvement to before because we are running all of these in parallel which speeds up execution and highlights more errors at once. Previously, tests run later in the pipeline would not get run at all until you make sure the "first" one passes. We also previously did not verify the MSRV of each crate, making the setting in the `Cargo.toml` rather pointless. The new `cross` job supersedes the existing `wasm` job. This is an improvement because we now also compile the crate for windows and MacOS. Something that wasn't checked before. We assume that checking MSRV and the tests under Linux is good enough. Hence, this job only checks for compile-errors. The new `feature_matrix` ensures we compile correctly with certain feature combinations. `libp2p` exposes a fair few feature-flags. Some of the combinations are worth checking independently. For the moment, this concerns only the executor related transports together with the executor flags but this list can easily be extended. The new `clippy` job runs for `stable` and `beta` rust. Clippy gets continuously extended with new lints. Up until now, we would only learn about those as soon as a new version of Rust is released and CI would run the new lints. This leads to unrelated failures in CI. Running clippy on with `beta` Rust gives us a heads-up of 6 weeks before these lints land on stable. Fixes #2951.
2022-11-18 22:04:16 +11:00
[PR 3090]: https://github.com/libp2p/rust-libp2p/pull/3090
feat: Better error reporting when features are disabled (#2972) In case support for e.g. RSA keys is disabled at compile-time, we will now print a better error message. For example: > Failed to dial Some(PeerId("QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt")): Failed to negotiate transport protocol(s): [(/dnsaddr/bootstrap.libp2p.io/p2p/QmcZf59bWwK5XFi76CZX8cbJ4BhTzzA3gU1ZjYZcYW3dwt): : Handshake failed: Handshake failed: Invalid public key: Key decoding error: RSA keys are unsupported)] Fixes #2971.
2022-11-23 11:51:47 +11:00
[PR 2972]: https://github.com/libp2p/rust-libp2p/pull/2972
refactor(core)!: remove `EitherError` in favor of `either::Either` (#3337) Defining our own `EitherError` type has no value now that `Either` provides the same implementation. Related: https://github.com/libp2p/rust-libp2p/issues/3271
2023-01-18 10:05:59 +11:00
[PR 3337]: https://github.com/libp2p/rust-libp2p/pull/3337
refactor(core)!: remove `EitherTransport` (#3338) We don't need to define our own type here, we can simply implement `Transport` on `either::Either`.
2023-01-18 11:58:09 +11:00
[PR 3338]: https://github.com/libp2p/rust-libp2p/pull/3338
refactor(core)!: remove `EitherUpgrade` (#3339) We don't need to define our own type here, we can simply implement `UpgradeInfo`, `InboundUpgrade` and `OutboundUpgrade` on `either::Either`.
2023-01-18 13:35:07 +11:00
[PR 3339]: https://github.com/libp2p/rust-libp2p/pull/3339
refactor(core)!: remove `EitherFuture2` (#3340) We can completely replace `EitherFuture2` with `EitherFuture`. `EitherFuture` itself cannot be removed for now because the `Future` implementation on `future::Either` forces both `Future`s to evaluate to the same type.
2023-01-18 21:17:18 +11:00
[PR 3340]: https://github.com/libp2p/rust-libp2p/pull/3340
refactor(core)!: remove `EitherOutput` (#3341) The trick with this one is to use `futures::Either` everywhere where we may wrap something that implements any of the `futures` traits. This includes the output of `EitherFuture` itself. We also need to implement `StreamMuxer` on `future::Either` because `StreamMuxer`s may be the the `Output` of `InboundUpgrade`.
2023-01-23 23:31:30 +11:00
[PR 3341]: https://github.com/libp2p/rust-libp2p/pull/3341
*: Don't leak `prost` dependency in error types (#3058) With the current design, a major version bump of `prost` leaks into all consumers of `prost-codec`.
2022-11-02 23:02:21 +11:00
*: Prepare v0.49.0 (#2931)
2022-10-14 15:30:16 +01:00
# 0.37.0
core/identity: Implement `Hash` and `Ord` for PublicKey (#2915) Co-authored-by: Thomas Eizinger <thomas@eizinger.io>
2022-09-22 21:35:42 +04:00
- Implement `Hash` and `Ord` for `PublicKey`. See [PR 2915].
*: Prepare v0.49.0 (#2931)
2022-10-14 15:30:16 +01:00
- Remove default features. If you previously depended on `secp256k1` or `ecdsa` you need to enable these explicitly
*: Remove default features from all crates (#2918) Remove default features. You need to enable required features explicitly now. As a quick workaround, you may want to use the new `full` feature which activates all features.
2022-09-30 01:32:22 +10:00
now. See [PR 2918].
core/muxer: Deprecate `StreamMuxerExt::next_{inbound,outbound}` (#3002)
2022-10-12 23:36:39 +11:00
- Deprecate `StreamMuxerExt::next_{inbound,outbound}`. See [PR 3002].
core/identity: Implement `Hash` and `Ord` for PublicKey (#2915) Co-authored-by: Thomas Eizinger <thomas@eizinger.io>
2022-09-22 21:35:42 +04:00
[PR 2915]: https://github.com/libp2p/rust-libp2p/pull/2915
*: Remove default features from all crates (#2918) Remove default features. You need to enable required features explicitly now. As a quick workaround, you may want to use the new `full` feature which activates all features.
2022-09-30 01:32:22 +10:00
[PR 2918]: https://github.com/libp2p/rust-libp2p/pull/2918
core/muxer: Deprecate `StreamMuxerExt::next_{inbound,outbound}` (#3002)
2022-10-12 23:36:39 +11:00
[PR 3002]: https://github.com/libp2p/rust-libp2p/pull/3002
core/identity: Implement `Hash` and `Ord` for PublicKey (#2915) Co-authored-by: Thomas Eizinger <thomas@eizinger.io>
2022-09-22 21:35:42 +04:00
*: Prepare v0.48.0 (#2869)
2022-09-07 09:44:51 +02:00
# 0.36.0
core/: Introduce `rsa` feature flag to avoid `ring` dependency (#2860) - Introduce `rsa` feature flag to `libp2p-core`. - Expose `rsa` feature in `libp2p`. - Add `rsa` feature to `libp2p` `default`.
2022-09-07 09:16:22 +03:00
- Make RSA keypair support optional. To enable RSA support, `rsa` feature should be enabled.
See [PR 2860].
core/upgrade/: Add `ReadyUpgrade` (#2855)
2022-09-07 17:08:23 +10:00
- Add `ReadyUpgrade`. See [PR 2855].
[PR 2855]: https://github.com/libp2p/rust-libp2p/pull/2855
core/: Introduce `rsa` feature flag to avoid `ring` dependency (#2860) - Introduce `rsa` feature flag to `libp2p-core`. - Expose `rsa` feature in `libp2p`. - Add `rsa` feature to `libp2p` `default`.
2022-09-07 09:16:22 +03:00
[PR 2860]: https://github.com/libp2p/rust-libp2p/pull/2860/
build(deps): Update p256 requirement from 0.10.0 to 0.11.0 (#2636) * build(deps): Update p256 requirement from 0.10.0 to 0.11.0 Updates the requirements on [p256](https://github.com/RustCrypto/elliptic-curves) to permit the latest version. - [Release notes](https://github.com/RustCrypto/elliptic-curves/releases) - [Commits](https://github.com/RustCrypto/elliptic-curves/commits/p256/v0.10.1) --- updated-dependencies: - dependency-name: p256 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> * core/: Bump version and add changelog entry Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Max Inden <mail@max-inden.de>
2022-08-23 09:51:58 +02:00
# 0.35.1
- Update to `p256` `v0.11.0`. See [PR 2636].
[PR 2636]: https://github.com/libp2p/rust-libp2p/pull/2636/
*: Prepare v0.47.0 (#2830)
2022-08-22 05:14:04 +02:00
# 0.35.0
core/muxing: Flatten `StreamMuxer` interface to `poll_{inbound,outbound,address_change,close}` (#2724) Instead of having a mix of `poll_event`, `poll_outbound` and `poll_close`, we flatten the entire interface of `StreamMuxer` into 4 individual functions: - `poll_inbound` - `poll_outbound` - `poll_address_change` - `poll_close` This design is closer to the design of other async traits like `AsyncRead` and `AsyncWrite`. It also allows us to delete the `StreamMuxerEvent`.
2022-07-18 04:20:11 +01:00
*: Update changelogs for prost dep update (#2851)
2022-08-30 03:03:54 -05:00
- Update prost requirement from 0.10 to 0.11 which no longer installs the protoc Protobuf compiler.
Thus you will need protoc installed locally. See [PR 2788].
core/muxing: Remove `Unpin` requirement from `StreamMuxer::Substream` (#2776)
2022-07-25 15:49:22 +01:00
- Drop `Unpin` requirement from `SubstreamBox`. See [PR 2762] and [PR 2776].
core/muxing: Drop `Sync` requirement for `StreamMuxer` on `StreamMuxerBox` (#2775) `StreamMuxerBox` is never shared across threads but owned by a single connection. Restricting it to be `Sync` unnecessarily limits the design space around the `StreamMuxer` trait and its implementations.
2022-07-27 08:23:07 +02:00
- Drop `Sync` requirement on `StreamMuxer` for constructing `StreamMuxerBox`. See [PR 2775].
core/muxing: Have functions on `StreamMuxer` take `Pin<&mut Self>` (#2765) Co-authored-by: Elena Frank <elena.frank@protonmail.com> Co-authored-by: Max Inden <mail@max-inden.de>
2022-08-03 15:12:11 +02:00
- Use `Pin<&mut Self>` as the receiver type for all `StreamMuxer` poll functions. See [PR 2765].
core/muxing: Generalise `StreamMuxer::poll_address_change` to `poll` (#2797) This is to allow general-purpose background work to be performed by implementations.
2022-08-16 04:50:17 +02:00
- Change `StreamMuxer` interface to be entirely poll-based. All functions on `StreamMuxer` now
require a `Context` and return `Poll`. This gives callers fine-grained control over what they
would like to make progress on. See [PR 2724] and [PR 2797].
core/muxing: Flatten `StreamMuxer` interface to `poll_{inbound,outbound,address_change,close}` (#2724) Instead of having a mix of `poll_event`, `poll_outbound` and `poll_close`, we flatten the entire interface of `StreamMuxer` into 4 individual functions: - `poll_inbound` - `poll_outbound` - `poll_address_change` - `poll_close` This design is closer to the design of other async traits like `AsyncRead` and `AsyncWrite`. It also allows us to delete the `StreamMuxerEvent`.
2022-07-18 04:20:11 +01:00
[PR 2724]: https://github.com/libp2p/rust-libp2p/pull/2724
core: fix PR number in changelog entry (#2769)
2022-07-23 20:48:52 +02:00
[PR 2762]: https://github.com/libp2p/rust-libp2p/pull/2762
core/muxing: Drop `Sync` requirement for `StreamMuxer` on `StreamMuxerBox` (#2775) `StreamMuxerBox` is never shared across threads but owned by a single connection. Restricting it to be `Sync` unnecessarily limits the design space around the `StreamMuxer` trait and its implementations.
2022-07-27 08:23:07 +02:00
[PR 2775]: https://github.com/libp2p/rust-libp2p/pull/2775
core/muxing: Remove `Unpin` requirement from `StreamMuxer::Substream` (#2776)
2022-07-25 15:49:22 +01:00
[PR 2776]: https://github.com/libp2p/rust-libp2p/pull/2776
core/muxing: Have functions on `StreamMuxer` take `Pin<&mut Self>` (#2765) Co-authored-by: Elena Frank <elena.frank@protonmail.com> Co-authored-by: Max Inden <mail@max-inden.de>
2022-08-03 15:12:11 +02:00
[PR 2765]: https://github.com/libp2p/rust-libp2p/pull/2765
core/muxing: Generalise `StreamMuxer::poll_address_change` to `poll` (#2797) This is to allow general-purpose background work to be performed by implementations.
2022-08-16 04:50:17 +02:00
[PR 2797]: https://github.com/libp2p/rust-libp2p/pull/2797
*: Update changelogs for prost dep update (#2851)
2022-08-30 03:03:54 -05:00
[PR 2788]: https://github.com/libp2p/rust-libp2p/pull/2788
core/muxing: Flatten `StreamMuxer` interface to `poll_{inbound,outbound,address_change,close}` (#2724) Instead of having a mix of `poll_event`, `poll_outbound` and `poll_close`, we flatten the entire interface of `StreamMuxer` into 4 individual functions: - `poll_inbound` - `poll_outbound` - `poll_address_change` - `poll_close` This design is closer to the design of other async traits like `AsyncRead` and `AsyncWrite`. It also allows us to delete the `StreamMuxerEvent`.
2022-07-18 04:20:11 +01:00
*: Prepare v0.46.0 (#2730)
2022-07-05 13:09:58 +02:00
# 0.34.0
core/muxing: Introduce `StreamMuxerEvent::map_inbound_stream` (#2691) Co-authored-by: Max Inden <mail@max-inden.de>
2022-06-15 21:33:32 +02:00
core/muxing: Force `StreamMuxer::Substream` to implement `Async{Read,Write}` (#2707) Co-authored-by: Max Inden <mail@max-inden.de>
2022-06-23 13:52:11 +02:00
- Remove `{read,write,flush,shutdown,destroy}_substream` functions from `StreamMuxer` trait
in favor of forcing `StreamMuxer::Substream` to implement `AsyncRead + AsyncWrite`. See [PR 2707].
core/muxing: Replace `Into<io::Error>` bound on `StreamMuxer` with `std::error::Error` (#2710) * core/muxing: Remove `Into<io::Error>` bound from `StreamMuxer::Error` This allows us to preserve the type information of a muxer's concrete error as long as possible. For `StreamMuxerBox`, we leverage `io::Error`'s capability of wrapping any error that implements `Into<Box<dyn Error>>`. * Use `?` in `Connection::poll` * Use `?` in `muxing::boxed::Wrap` * Use `futures::ready!` in `muxing::boxed::Wrap` * Fill PR number into changelog * Put `Error + Send + Sync` bounds directly on `StreamMuxer::Error` * Move `Send + Sync` bounds to higher layers * Use `map_inbound_stream` helper * Update changelog to match new implementation
2022-06-24 08:26:49 +02:00
- Replace `Into<std::io::Error>` bound on `StreamMuxer::Error` with `std::error::Error`. See [PR 2710].
core/muxing: Introduce `StreamMuxerEvent::map_inbound_stream` (#2691) Co-authored-by: Max Inden <mail@max-inden.de>
2022-06-15 21:33:32 +02:00
core/src/transport: Poll Transport directly, remove Transport::Listener (#2652) Remove the concept of individual `Transport::Listener` streams from `Transport`. Instead the `Transport` is polled directly via `Transport::poll`. The `Transport` is now responsible for driving its listeners.
2022-07-04 04:16:57 +02:00
- Remove the concept of individual `Transport::Listener` streams from `Transport`.
Instead the `Transport` is polled directly via `Transport::poll`. The
`Transport` is now responsible for driving its listeners. See [PR 2652].
core/muxing: Introduce `StreamMuxerEvent::map_inbound_stream` (#2691) Co-authored-by: Max Inden <mail@max-inden.de>
2022-06-15 21:33:32 +02:00
[PR 2691]: https://github.com/libp2p/rust-libp2p/pull/2691
core/muxing: Force `StreamMuxer::Substream` to implement `Async{Read,Write}` (#2707) Co-authored-by: Max Inden <mail@max-inden.de>
2022-06-23 13:52:11 +02:00
[PR 2707]: https://github.com/libp2p/rust-libp2p/pull/2707
core/muxing: Replace `Into<io::Error>` bound on `StreamMuxer` with `std::error::Error` (#2710) * core/muxing: Remove `Into<io::Error>` bound from `StreamMuxer::Error` This allows us to preserve the type information of a muxer's concrete error as long as possible. For `StreamMuxerBox`, we leverage `io::Error`'s capability of wrapping any error that implements `Into<Box<dyn Error>>`. * Use `?` in `Connection::poll` * Use `?` in `muxing::boxed::Wrap` * Use `futures::ready!` in `muxing::boxed::Wrap` * Fill PR number into changelog * Put `Error + Send + Sync` bounds directly on `StreamMuxer::Error` * Move `Send + Sync` bounds to higher layers * Use `map_inbound_stream` helper * Update changelog to match new implementation
2022-06-24 08:26:49 +02:00
[PR 2710]: https://github.com/libp2p/rust-libp2p/pull/2710
core/src/transport: Poll Transport directly, remove Transport::Listener (#2652) Remove the concept of individual `Transport::Listener` streams from `Transport`. Instead the `Transport` is polled directly via `Transport::poll`. The `Transport` is now responsible for driving its listeners.
2022-07-04 04:16:57 +02:00
[PR 2652]: https://github.com/libp2p/rust-libp2p/pull/2652
core/muxing: Introduce `StreamMuxerEvent::map_inbound_stream` (#2691) Co-authored-by: Max Inden <mail@max-inden.de>
2022-06-15 21:33:32 +02:00
*: Prepare v0.45.0 (#2662)
2022-05-31 13:12:53 +02:00
# 0.33.0
{core,swarm}/: Don't require `Transport: Clone` and take `&mut` (#2529) Previously `libp2p-swarm` required a `Transport` to be `Clone`. Methods on `Transport`, e.g. `Transport::dial` would take ownership, requiring e.g. a `Clone::clone` before calling `Transport::dial`. The requirement of `Transport` to be `Clone` is no longer needed in `libp2p-swarm`. E.g. concurrent dialing can be done without a clone per dial. This commit removes the requirement of `Clone` for `Transport` in `libp2p-swarm`. As a follow-up methods on `Transport` no longer take ownership, but instead a mutable reference (`&mut self`). On the one hand this simplifies `libp2p-swarm`, on the other it simplifies implementations of `Transport`.
2022-04-06 20:23:16 +02:00
- Have methods on `Transport` take `&mut self` instead of `self`. See [PR 2529].
core/muxing: Remove the `StreamMuxer::flush_all` function (#2669) `libp2p-core` provides the `StreamMuxer` abstraction so it can provide functionality that abstracts over this trait. We never use the `flush_all` function as part of our abstractions. No one else is going to use it so we can remove it from the abstraction.
2022-05-29 17:23:13 +02:00
- Remove `StreamMuxer::flush_all`. See [PR 2669].
core/muxing: Rename `close` to `poll_close` (#2666) It is common practise to prefix functions that return a `Poll` with `poll_`.
2022-05-29 16:27:40 +02:00
- Rename `StreamMuxer::close` to `StreamMuxer::poll_close`. See [PR 2666].
core/src/muxing: Remove deprecated function (#2665)
2022-05-23 16:56:59 +02:00
- Remove deprecated function `StreamMuxer::is_remote_acknowledged`. See [PR 2665].
{core,swarm}/: Don't require `Transport: Clone` and take `&mut` (#2529) Previously `libp2p-swarm` required a `Transport` to be `Clone`. Methods on `Transport`, e.g. `Transport::dial` would take ownership, requiring e.g. a `Clone::clone` before calling `Transport::dial`. The requirement of `Transport` to be `Clone` is no longer needed in `libp2p-swarm`. E.g. concurrent dialing can be done without a clone per dial. This commit removes the requirement of `Clone` for `Transport` in `libp2p-swarm`. As a follow-up methods on `Transport` no longer take ownership, but instead a mutable reference (`&mut self`). On the one hand this simplifies `libp2p-swarm`, on the other it simplifies implementations of `Transport`.
2022-04-06 20:23:16 +02:00
[PR 2529]: https://github.com/libp2p/rust-libp2p/pull/2529
core/muxing: Rename `close` to `poll_close` (#2666) It is common practise to prefix functions that return a `Poll` with `poll_`.
2022-05-29 16:27:40 +02:00
[PR 2666]: https://github.com/libp2p/rust-libp2p/pull/2666
core/src/muxing: Remove deprecated function (#2665)
2022-05-23 16:56:59 +02:00
[PR 2665]: https://github.com/libp2p/rust-libp2p/pull/2665
core/muxing: Remove the `StreamMuxer::flush_all` function (#2669) `libp2p-core` provides the `StreamMuxer` abstraction so it can provide functionality that abstracts over this trait. We never use the `flush_all` function as part of our abstractions. No one else is going to use it so we can remove it from the abstraction.
2022-05-29 17:23:13 +02:00
[PR 2669]: https://github.com/libp2p/rust-libp2p/pull/2669
{core,swarm}/: Don't require `Transport: Clone` and take `&mut` (#2529) Previously `libp2p-swarm` required a `Transport` to be `Clone`. Methods on `Transport`, e.g. `Transport::dial` would take ownership, requiring e.g. a `Clone::clone` before calling `Transport::dial`. The requirement of `Transport` to be `Clone` is no longer needed in `libp2p-swarm`. E.g. concurrent dialing can be done without a clone per dial. This commit removes the requirement of `Clone` for `Transport` in `libp2p-swarm`. As a follow-up methods on `Transport` no longer take ownership, but instead a mutable reference (`&mut self`). On the one hand this simplifies `libp2p-swarm`, on the other it simplifies implementations of `Transport`.
2022-04-06 20:23:16 +02:00
*: Prepare libp2p v0.44.0 (#2604)
2022-04-04 18:27:41 +02:00
# 0.32.1
core/: Add `PeerId::try_from_multiaddr` (#2551)
2022-03-10 20:43:16 +11:00
- Add `PeerId::try_from_multiaddr` to extract a `PeerId` from a `Multiaddr` that ends in `/p2p/<peer-id>`.
*: Prepare v0.43.0 (#2531)
2022-02-22 14:05:19 +01:00
# 0.32.0 [2022-02-22]
*: Update multihash and multiaddr (#2469) Co-authored-by: Max Inden <mail@max-inden.de>
2022-02-03 16:38:41 +00:00
{core,swarm}: Remove Network abstraction (#2492) This commit removes the `Network` abstraction, thus managing `Listeners` and the connection `Pool` in `Swarm` directly. This is done under the assumption that noone uses the `Network` abstraction directly, but instead everyone always uses it through `Swarm`. Both `Listeners` and `Pool` are moved from `libp2p-core` into `libp2p-swarm`. Given that they are no longer exposed via `Network`, they can be treated as an implementation detail of `libp2p-swarm` and `Swarm`. This change does not include any behavioural changes. This change has the followin benefits: - Removal of `NetworkEvent`, which was mostly an isomorphism of `SwarmEvent`. - Removal of the never-directly-used `Network` abstraction. - Removal of now obsolete verbose `Peer` (`core/src/network/peer.rs`) construct. - Removal of `libp2p-core` `DialOpts`, which is a direct mapping of `libp2p-swarm` `DialOpts`. - Allowing breaking changes to the connection handling and `Swarm` API interface without a breaking change in `libp2p-core` and thus a without a breaking change in `/transport` protocols. This change enables the following potential future changes: - Removal of `NodeHandler` and `ConnectionHandler`. Thus allowing to rename `ProtocolsHandler` into `ConnectionHandler`. - Moving `NetworkBehaviour` and `ProtocolsHandler` into `libp2p-core`, having `libp2p-xxx` protocol crates only depend on `libp2p-core` and thus allowing general breaking changes to `Swarm` without breaking all `libp2p-xxx` crates.
2022-02-13 21:57:38 +01:00
- Remove `Network`. `libp2p-core` is from now on an auxiliary crate only. Users
that have previously used `Network` only, will need to use `Swarm` instead. See
[PR 2492].
*: Update multihash and multiaddr (#2469) Co-authored-by: Max Inden <mail@max-inden.de>
2022-02-03 16:38:41 +00:00
- Update to `multiaddr` `v0.14.0`.
- Update to `multihash` `v0.16.0`.
core/: Add Display implementation for DialError (#2473) Co-authored-by: Frederik Baetens <baetens.fr@gmail.com>
2022-02-03 12:49:01 +01:00
- Implement `Display` on `DialError`. See [PR 2456].
build(deps): Update parking_lot requirement from 0.11.0 to 0.12.0 (#2463) * build(deps): Update parking_lot requirement from 0.11.0 to 0.12.0 Updates the requirements on [parking_lot](https://github.com/Amanieu/parking_lot) to permit the latest version. - [Release notes](https://github.com/Amanieu/parking_lot/releases) - [Changelog](https://github.com/Amanieu/parking_lot/blob/master/CHANGELOG.md) - [Commits](https://github.com/Amanieu/parking_lot/compare/0.11.0...0.12.0) --- updated-dependencies: - dependency-name: parking_lot dependency-type: direct:production ... Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Max Inden <mail@max-inden.de>
2022-02-16 15:16:04 +01:00
- Update to `parking_lot` `v0.12.0`. See [PR 2463].
core/src/: Validate PeerRecord signature matching peer ID (#2491) Co-authored-by: Marco Munizaga <git@marcopolo.io>
2022-02-09 16:39:02 +01:00
- Validate PeerRecord signature matching peer ID. See [RUSTSEC-2022-0009].
core/src: Take ref of key in SignedEnvelope & PeerRecord (#2516)
2022-02-15 23:47:32 +01:00
- Don't take ownership of key in `PeerRecord::new` and `SignedEnvelope::new`. See [PR 2516].
core/src/signed_envelope/: Return signing key with payload (#2522) Remove `SignedEnvelope::payload` in favor of `SignedEnvelope::payload_and_signing_key`. The caller is expected to check that the returned signing key makes sense in the payload's context.
2022-02-21 01:45:57 -08:00
- Remove `SignedEnvelope::payload` in favor of
`SignedEnvelope::payload_and_signing_key`. The caller is expected to check
that the returned signing key makes sense in the payload's context. See [PR 2522].
core/: Add Display implementation for DialError (#2473) Co-authored-by: Frederik Baetens <baetens.fr@gmail.com>
2022-02-03 12:49:01 +01:00
[PR 2456]: https://github.com/libp2p/rust-libp2p/pull/2456
core/src/: Validate PeerRecord signature matching peer ID (#2491) Co-authored-by: Marco Munizaga <git@marcopolo.io>
2022-02-09 16:39:02 +01:00
[RUSTSEC-2022-0009]: https://rustsec.org/advisories/RUSTSEC-2022-0009.html
{core,swarm}: Remove Network abstraction (#2492) This commit removes the `Network` abstraction, thus managing `Listeners` and the connection `Pool` in `Swarm` directly. This is done under the assumption that noone uses the `Network` abstraction directly, but instead everyone always uses it through `Swarm`. Both `Listeners` and `Pool` are moved from `libp2p-core` into `libp2p-swarm`. Given that they are no longer exposed via `Network`, they can be treated as an implementation detail of `libp2p-swarm` and `Swarm`. This change does not include any behavioural changes. This change has the followin benefits: - Removal of `NetworkEvent`, which was mostly an isomorphism of `SwarmEvent`. - Removal of the never-directly-used `Network` abstraction. - Removal of now obsolete verbose `Peer` (`core/src/network/peer.rs`) construct. - Removal of `libp2p-core` `DialOpts`, which is a direct mapping of `libp2p-swarm` `DialOpts`. - Allowing breaking changes to the connection handling and `Swarm` API interface without a breaking change in `libp2p-core` and thus a without a breaking change in `/transport` protocols. This change enables the following potential future changes: - Removal of `NodeHandler` and `ConnectionHandler`. Thus allowing to rename `ProtocolsHandler` into `ConnectionHandler`. - Moving `NetworkBehaviour` and `ProtocolsHandler` into `libp2p-core`, having `libp2p-xxx` protocol crates only depend on `libp2p-core` and thus allowing general breaking changes to `Swarm` without breaking all `libp2p-xxx` crates.
2022-02-13 21:57:38 +01:00
[PR 2492]: https://github.com/libp2p/rust-libp2p/pull/2492
core/src: Take ref of key in SignedEnvelope & PeerRecord (#2516)
2022-02-15 23:47:32 +01:00
[PR 2516]: https://github.com/libp2p/rust-libp2p/pull/2516
build(deps): Update parking_lot requirement from 0.11.0 to 0.12.0 (#2463) * build(deps): Update parking_lot requirement from 0.11.0 to 0.12.0 Updates the requirements on [parking_lot](https://github.com/Amanieu/parking_lot) to permit the latest version. - [Release notes](https://github.com/Amanieu/parking_lot/releases) - [Changelog](https://github.com/Amanieu/parking_lot/blob/master/CHANGELOG.md) - [Commits](https://github.com/Amanieu/parking_lot/compare/0.11.0...0.12.0) --- updated-dependencies: - dependency-name: parking_lot dependency-type: direct:production ... Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Max Inden <mail@max-inden.de>
2022-02-16 15:16:04 +01:00
[PR 2463]: https://github.com/libp2p/rust-libp2p/pull/2463/
core/src/signed_envelope/: Return signing key with payload (#2522) Remove `SignedEnvelope::payload` in favor of `SignedEnvelope::payload_and_signing_key`. The caller is expected to check that the returned signing key makes sense in the payload's context.
2022-02-21 01:45:57 -08:00
[PR 2522]: https://github.com/libp2p/rust-libp2p/pull/2522
core/: Add Display implementation for DialError (#2473) Co-authored-by: Frederik Baetens <baetens.fr@gmail.com>
2022-02-03 12:49:01 +01:00
*: Prepare v0.42.0 (#2440)
2022-01-27 11:29:09 +01:00
# 0.31.0 [2022-01-27]
swarm/: Patch reporting on banned peer connections (#2350) Don't report events of a connection to the `NetworkBehaviour`, if connection has been established while the remote peer was banned. Among other guarantees this upholds that `NetworkBehaviour::inject_event` is never called without a previous `NetworkBehaviour::inject_connection_established` for said connection. Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-26 10:48:12 -05:00
*: Migrate to Rust 2021 edition (#2339) Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-26 09:34:58 -07:00
- Update dependencies.
swarm/: Patch reporting on banned peer connections (#2350) Don't report events of a connection to the `NetworkBehaviour`, if connection has been established while the remote peer was banned. Among other guarantees this upholds that `NetworkBehaviour::inject_event` is never called without a previous `NetworkBehaviour::inject_connection_established` for said connection. Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-26 10:48:12 -05:00
- Report concrete connection IDs in `NetworkEvent::ConnectionEstablished` and
`NetworkEvent::ConnectionClosed` (see [PR 2350]).
*: Migrate to Rust 2021 edition (#2339) Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-26 09:34:58 -07:00
- Migrate to Rust edition 2021 (see [PR 2339]).
core/: Add support for ECDSA identities (#2352) Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-30 17:47:35 +01:00
- Add support for ECDSA identities (see [PR 2352]).
core/src/connection: Add ConnectedPoint::is_relayed (#2392) Add convenience function `is_relayed` to `ConnectedPoint`, determining whether a connection is relayed based on whether it contains a `Protocol::P2pCircuit`.
2021-12-19 14:50:55 +01:00
- Add `ConnectedPoint::is_relayed` (see [PR 2392]).
{core,swarm}/: Allow configuring dial concurrency factor per dial (#2404) Enable a `NetworkBehaviour` or a user via `Swarm::dial` to override the dial concurrency factor per dial. This is especially relevant in the case of libp2p-autonat where one wants to probe addresses in sequence to reduce the amount of work a remote peer can force onto the local node. To enable the above, this commit also: - Introduces `libp2p_core::DialOpts` mirroring `libp2p_swarm::DialOpts`. Passed as an argument to `Network::dial`. - Removes `Peer::dial` in favor of `Network::dial`. - Simplifies `Swarm::dial_with_handler`. The introduction of `libp2p_core::DialOpts` will be useful beyond this feature, e.g. for https://github.com/libp2p/rust-libp2p/pull/2363. In the long run I would like to move and merge `libp2p_core::Network` and `libp2p_core::Pool` into `libp2p_swarm::Swarm` thus deduplicating `libp2p_core::DialOpts` and `libp2p_swarm::DialOpts`. Fixes #2385.
2022-01-13 18:07:07 +01:00
- Enable overriding _dial concurrency factor_ per dial via
`DialOpts::override_dial_concurrency_factor`.
*: Rework reporting of invalid and wrong PeerIds (#2441) Previously, the negotiated PeerId was included in the swarm event and inject_dial_failure’s arguments while the expected one was absent. This patch adds the negotiated PeerId to the DialError and includes the expected one in the notifications. Co-authored-by: Roland Kuhn <rk@rkuhn.info>
2022-01-18 21:21:11 +01:00
- Introduces `libp2p_core::DialOpts` mirroring `libp2p_swarm::DialOpts`.
{core,swarm}/: Allow configuring dial concurrency factor per dial (#2404) Enable a `NetworkBehaviour` or a user via `Swarm::dial` to override the dial concurrency factor per dial. This is especially relevant in the case of libp2p-autonat where one wants to probe addresses in sequence to reduce the amount of work a remote peer can force onto the local node. To enable the above, this commit also: - Introduces `libp2p_core::DialOpts` mirroring `libp2p_swarm::DialOpts`. Passed as an argument to `Network::dial`. - Removes `Peer::dial` in favor of `Network::dial`. - Simplifies `Swarm::dial_with_handler`. The introduction of `libp2p_core::DialOpts` will be useful beyond this feature, e.g. for https://github.com/libp2p/rust-libp2p/pull/2363. In the long run I would like to move and merge `libp2p_core::Network` and `libp2p_core::Pool` into `libp2p_swarm::Swarm` thus deduplicating `libp2p_core::DialOpts` and `libp2p_swarm::DialOpts`. Fixes #2385.
2022-01-13 18:07:07 +01:00
Passed as an argument to `Network::dial`.
*: Rework reporting of invalid and wrong PeerIds (#2441) Previously, the negotiated PeerId was included in the swarm event and inject_dial_failure’s arguments while the expected one was absent. This patch adds the negotiated PeerId to the DialError and includes the expected one in the notifications. Co-authored-by: Roland Kuhn <rk@rkuhn.info>
2022-01-18 21:21:11 +01:00
- Removes `Peer::dial` in favor of `Network::dial`.
{core,swarm}/: Allow configuring dial concurrency factor per dial (#2404) Enable a `NetworkBehaviour` or a user via `Swarm::dial` to override the dial concurrency factor per dial. This is especially relevant in the case of libp2p-autonat where one wants to probe addresses in sequence to reduce the amount of work a remote peer can force onto the local node. To enable the above, this commit also: - Introduces `libp2p_core::DialOpts` mirroring `libp2p_swarm::DialOpts`. Passed as an argument to `Network::dial`. - Removes `Peer::dial` in favor of `Network::dial`. - Simplifies `Swarm::dial_with_handler`. The introduction of `libp2p_core::DialOpts` will be useful beyond this feature, e.g. for https://github.com/libp2p/rust-libp2p/pull/2363. In the long run I would like to move and merge `libp2p_core::Network` and `libp2p_core::Pool` into `libp2p_swarm::Swarm` thus deduplicating `libp2p_core::DialOpts` and `libp2p_swarm::DialOpts`. Fixes #2385.
2022-01-13 18:07:07 +01:00
See [PR 2404].
*: Add Serialize and Deserialize to PeerId gossipsub MessageId and kad Key (#2408) Co-authored-by: Max Inden <mail@max-inden.de>
2022-01-11 15:38:51 -05:00
- Implement `Serialize` and `Deserialize` for `PeerId` (see [PR 2408])
*: Rework reporting of invalid and wrong PeerIds (#2441) Previously, the negotiated PeerId was included in the swarm event and inject_dial_failure’s arguments while the expected one was absent. This patch adds the negotiated PeerId to the DialError and includes the expected one in the notifications. Co-authored-by: Roland Kuhn <rk@rkuhn.info>
2022-01-18 21:21:11 +01:00
- Report negotiated and expected `PeerId` as well as remote address in
`DialError::WrongPeerId` (see [PR 2428]).
core/src/transport: Add `Transport::dial_as_listener` (#2363) Allows `NetworkBehaviour` implementations to dial a peer, but instruct the dialed connection to be upgraded as if it were the listening endpoint. This is needed when establishing direct connections through NATs and/or Firewalls (hole punching). When hole punching via TCP (QUIC is different but similar) both ends dial the other at the same time resulting in a simultaneously opened TCP connection. To disambiguate who is the dialer and who the listener there are two options: 1. Use the Simultaneous Open Extension of Multistream Select. See [sim-open] specification and [sim-open-rust] Rust implementation. 2. Disambiguate the role (dialer or listener) based on the role within the DCUtR [dcutr] protocol. More specifically the node initiating the DCUtR process will act as a listener and the other as a dialer. This commit enables (2), i.e. enables the DCUtR protocol to specify the role used once the connection is established. While on the positive side (2) requires one round trip less than (1), on the negative side (2) only works for coordinated simultaneous dials. I.e. when a simultaneous dial happens by chance, and not coordinated via DCUtR, the connection attempt fails when only (2) is in place. [sim-open]: https://github.com/libp2p/specs/blob/master/connections/simopen.md [sim-open-rust]: https://github.com/libp2p/rust-libp2p/pull/2066 [dcutr]: https://github.com/libp2p/specs/blob/master/relay/DCUtR.md
2022-01-17 16:35:14 +01:00
- Allow overriding role when dialing. This option is needed for NAT and firewall
hole punching.
- Add `Transport::dial_as_listener`. As `Transport::dial` but
overrides the role of the local node on the connection . I.e. has the
local node act as a listener on the outgoing connection.
- Add `override_role` option to `DialOpts`.
See [PR 2363].
*: Migrate to Rust 2021 edition (#2339) Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-26 09:34:58 -07:00
[PR 2339]: https://github.com/libp2p/rust-libp2p/pull/2339
core/: Add support for ECDSA identities (#2352) Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-30 17:47:35 +01:00
[PR 2350]: https://github.com/libp2p/rust-libp2p/pull/2350
[PR 2352]: https://github.com/libp2p/rust-libp2p/pull/2352
core/src/connection: Add ConnectedPoint::is_relayed (#2392) Add convenience function `is_relayed` to `ConnectedPoint`, determining whether a connection is relayed based on whether it contains a `Protocol::P2pCircuit`.
2021-12-19 14:50:55 +01:00
[PR 2392]: https://github.com/libp2p/rust-libp2p/pull/2392
{core,swarm}/: Allow configuring dial concurrency factor per dial (#2404) Enable a `NetworkBehaviour` or a user via `Swarm::dial` to override the dial concurrency factor per dial. This is especially relevant in the case of libp2p-autonat where one wants to probe addresses in sequence to reduce the amount of work a remote peer can force onto the local node. To enable the above, this commit also: - Introduces `libp2p_core::DialOpts` mirroring `libp2p_swarm::DialOpts`. Passed as an argument to `Network::dial`. - Removes `Peer::dial` in favor of `Network::dial`. - Simplifies `Swarm::dial_with_handler`. The introduction of `libp2p_core::DialOpts` will be useful beyond this feature, e.g. for https://github.com/libp2p/rust-libp2p/pull/2363. In the long run I would like to move and merge `libp2p_core::Network` and `libp2p_core::Pool` into `libp2p_swarm::Swarm` thus deduplicating `libp2p_core::DialOpts` and `libp2p_swarm::DialOpts`. Fixes #2385.
2022-01-13 18:07:07 +01:00
[PR 2404]: https://github.com/libp2p/rust-libp2p/pull/2404
*: Add Serialize and Deserialize to PeerId gossipsub MessageId and kad Key (#2408) Co-authored-by: Max Inden <mail@max-inden.de>
2022-01-11 15:38:51 -05:00
[PR 2408]: https://github.com/libp2p/rust-libp2p/pull/2408
*: Rework reporting of invalid and wrong PeerIds (#2441) Previously, the negotiated PeerId was included in the swarm event and inject_dial_failure’s arguments while the expected one was absent. This patch adds the negotiated PeerId to the DialError and includes the expected one in the notifications. Co-authored-by: Roland Kuhn <rk@rkuhn.info>
2022-01-18 21:21:11 +01:00
[PR 2428]: https://github.com/libp2p/rust-libp2p/pull/2428
core/src/transport: Add `Transport::dial_as_listener` (#2363) Allows `NetworkBehaviour` implementations to dial a peer, but instruct the dialed connection to be upgraded as if it were the listening endpoint. This is needed when establishing direct connections through NATs and/or Firewalls (hole punching). When hole punching via TCP (QUIC is different but similar) both ends dial the other at the same time resulting in a simultaneously opened TCP connection. To disambiguate who is the dialer and who the listener there are two options: 1. Use the Simultaneous Open Extension of Multistream Select. See [sim-open] specification and [sim-open-rust] Rust implementation. 2. Disambiguate the role (dialer or listener) based on the role within the DCUtR [dcutr] protocol. More specifically the node initiating the DCUtR process will act as a listener and the other as a dialer. This commit enables (2), i.e. enables the DCUtR protocol to specify the role used once the connection is established. While on the positive side (2) requires one round trip less than (1), on the negative side (2) only works for coordinated simultaneous dials. I.e. when a simultaneous dial happens by chance, and not coordinated via DCUtR, the connection attempt fails when only (2) is in place. [sim-open]: https://github.com/libp2p/specs/blob/master/connections/simopen.md [sim-open-rust]: https://github.com/libp2p/rust-libp2p/pull/2066 [dcutr]: https://github.com/libp2p/specs/blob/master/relay/DCUtR.md
2022-01-17 16:35:14 +01:00
[PR 2363]: https://github.com/libp2p/rust-libp2p/pull/2363
swarm/: Patch reporting on banned peer connections (#2350) Don't report events of a connection to the `NetworkBehaviour`, if connection has been established while the remote peer was banned. Among other guarantees this upholds that `NetworkBehaviour::inject_event` is never called without a previous `NetworkBehaviour::inject_connection_established` for said connection. Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-26 10:48:12 -05:00
*: Prepare v0.41.0 (#2342)
2021-11-16 16:39:42 +01:00
# 0.30.1 [2021-11-16]
*: Enable libp2p to run via wasm32-unknown-unknown in the browser (#2320) Changes needed to get libp2p to run via `wasm32-unknown-unknown` in the browser (both main thread and inside web workers). Replaces wasm-timer with futures-timer and instant. Co-authored-by: Oliver Wangler <oliver@wngr.de>
2021-10-30 12:41:30 +02:00
- Use `instant` instead of `wasm-timer` (see [PR 2245]).
[PR 2245]: https://github.com/libp2p/rust-libp2p/pull/2245
Merge branch 'libp2p/v0.40' into master (#2324) * *: Prepare v0.40.0 release (#2323) * Cargo.toml: Remove rc suffix
2021-11-02 20:40:48 +01:00
# 0.30.0 [2021-11-01]
to/into consistency for PublicKey and PeerId (#2145) - Change `PublicKey::into_protobuf_encoding` to `PublicKey::to_protobuf_encoding`. - Change `PublicKey::into_peer_id` to `PublicKey::to_peer_id`. - Change `PeerId::from_public_key(PublicKey)` to `PeerId::from_public_key(&PublicKey)`. - Add `From<&PublicKey> for PeerId`. Co-authored-by: Max Inden <mail@max-inden.de>
2021-07-22 22:34:13 +02:00
core: Add a total established connection limit (#2137) Co-authored-by: Max Inden <mail@max-inden.de>
2021-07-31 03:22:53 +10:00
- Add `ConnectionLimit::with_max_established` (see [PR 2137]).
core/: Add Keypair::to_protobuf_encoding (#2142) Co-authored-by: Max Inden <mail@max-inden.de>
2021-07-28 17:59:08 +02:00
- Add `Keypair::to_protobuf_encoding` (see [PR 2142]).
to/into consistency for PublicKey and PeerId (#2145) - Change `PublicKey::into_protobuf_encoding` to `PublicKey::to_protobuf_encoding`. - Change `PublicKey::into_peer_id` to `PublicKey::to_peer_id`. - Change `PeerId::from_public_key(PublicKey)` to `PeerId::from_public_key(&PublicKey)`. - Add `From<&PublicKey> for PeerId`. Co-authored-by: Max Inden <mail@max-inden.de>
2021-07-22 22:34:13 +02:00
- Change `PublicKey::into_protobuf_encoding` to `PublicKey::to_protobuf_encoding` (see [PR 2145]).
- Change `PublicKey::into_peer_id` to `PublicKey::to_peer_id` (see [PR 2145]).
- Change `PeerId::from_public_key(PublicKey)` to `PeerId::from_public_key(&PublicKey)` (see [PR 2145]).
- Add `From<&PublicKey> for PeerId` (see [PR 2145]).
core/: Remove TInEvent and TOutEvent (#2183) TInEvent and TOutEvent are implied through THandler and thus superflucious. Both are removed in favor of a derivation through THandler.
2021-08-11 12:41:28 +02:00
- Remove `TInEvent` and `TOutEvent` trait paramters on most public types.
`TInEvent` and `TOutEvent` are implied through `THandler` and thus
superflucious. Both are removed in favor of a derivation through `THandler`
(see [PR 2183]).
- Require `ConnectionHandler::{InEvent,OutEvent,Error}` to implement `Debug`
(see [PR 2183]).
core/: Remove DisconnectedPeer::set_connected and Pool::add (#2195) This logic seems to be a leftover of https://github.com/libp2p/rust-libp2p/pull/889 and unused today.
2021-08-19 20:17:18 +02:00
- Remove `DisconnectedPeer::set_connected` and `Pool::add` (see [PR 2195]).
*: Dial with handler and return handler on error and closed (#2191) Require `NetworkBehaviourAction::{DialPeer,DialAddress}` to contain a `ProtocolsHandler`. This allows a behaviour to attach custom state to its handler. The behaviour would no longer need to track this state separately during connection establishment, thus reducing state required in a behaviour. E.g. in the case of `libp2p-kad` the behaviour can include a `GetRecord` request in its handler, or e.g. in the case of `libp2p-request-response` the behaviour can include the first request in the handler. Return `ProtocolsHandler` on connection error and close. This allows a behaviour to extract its custom state previously included in the handler on connection failure and connection closing. E.g. in the case of `libp2p-kad` the behaviour could extract the attached `GetRecord` from the handler of the failed connection and then start another connection attempt with a new handler with the same `GetRecord` or bubble up an error to the user. Co-authored-by: Thomas Eizinger <thomas@eizinger.io>
2021-08-31 17:00:51 +02:00
- Report `ConnectionLimit` error through `ConnectionError` and thus through
`NetworkEvent::ConnectionClosed` instead of previously through
`PendingConnectionError` and thus `NetworkEvent::{IncomingConnectionError,
DialError}` (see [PR 2191]).
- Report abortion of pending connection through `DialError`,
`UnknownPeerDialError` or `IncomingConnectionError` (see [PR 2191]).
core/: Remove DisconnectedPeer::set_connected and Pool::add (#2195) This logic seems to be a leftover of https://github.com/libp2p/rust-libp2p/pull/889 and unused today.
2021-08-19 20:17:18 +02:00
core/: Remove deprecated read/write functions (#2213) Co-authored-by: Max Inden <mail@max-inden.de>
2021-09-06 16:04:30 +10:00
- Remove deprecated functions `upgrade::write_one`, `upgrade::write_with_len_prefix`
and `upgrade::read_one` (see [PR 2213]).
protocols/rendezvous: Implement protocol (#2107) Implement the libp2p rendezvous protocol. > A lightweight mechanism for generalized peer discovery. It can be used for bootstrap purposes, real time peer discovery, application specific routing, and so on. Co-authored-by: rishflab <rishflab@hotmail.com> Co-authored-by: Daniel Karzel <daniel@comit.network>
2021-09-08 00:36:52 +10:00
- Add `SignedEnvelope` and `PeerRecord` according to [RFC0002] and [RFC0003]
(see [PR 2107]).
core/connection/listeners: Create event on remove_listener (#2261) Create a `ListenersEvent::Closed` when a listener is removed via `Swarm::remove_listener`. This makes it more consistent with `Swarm::listen_on`, and also informs the Swarm about the associated expired addresses. Co-authored-by: Max Inden <mail@max-inden.de>
2021-10-11 22:38:55 +02:00
- Report `ListenersEvent::Closed` when dropping a listener in `ListenersStream::remove_listener`,
return `bool` instead of `Result<(), ()>` (see [PR 2261]).
core/: Concurrent dial attempts (#2248) Concurrently dial address candidates within a single dial attempt. Main motivation for this feature is to increase success rate on hole punching (see https://github.com/libp2p/rust-libp2p/issues/1896#issuecomment-885894496 for details). Though, as a nice side effect, as one would expect, it does improve connection establishment time. Cleanups and fixes done along the way: - Merge `pool.rs` and `manager.rs`. - Instead of manually implementing state machines in `task.rs` use `async/await`. - Fix bug where `NetworkBehaviour::inject_connection_closed` is called without a previous `NetworkBehaviour::inject_connection_established` (see https://github.com/libp2p/rust-libp2p/issues/2242). - Return handler to behaviour on incoming connection limit error. Missed in https://github.com/libp2p/rust-libp2p/issues/2242.
2021-10-14 18:05:07 +02:00
- Concurrently dial address candidates within a single dial attempt (see [PR 2248]) configured
via `Network::with_dial_concurrency_factor`.
- On success of a single address, provide errors of the thus far failed dials via
`NetworkEvent::ConnectionEstablished::outgoing`.
- On failure of all addresses, provide the errors via `NetworkEvent::DialError`.
to/into consistency for PublicKey and PeerId (#2145) - Change `PublicKey::into_protobuf_encoding` to `PublicKey::to_protobuf_encoding`. - Change `PublicKey::into_peer_id` to `PublicKey::to_peer_id`. - Change `PeerId::from_public_key(PublicKey)` to `PeerId::from_public_key(&PublicKey)`. - Add `From<&PublicKey> for PeerId`. Co-authored-by: Max Inden <mail@max-inden.de>
2021-07-22 22:34:13 +02:00
[PR 2145]: https://github.com/libp2p/rust-libp2p/pull/2145
core/: Remove deprecated read/write functions (#2213) Co-authored-by: Max Inden <mail@max-inden.de>
2021-09-06 16:04:30 +10:00
[PR 2213]: https://github.com/libp2p/rust-libp2p/pull/2213
core/: Add Keypair::to_protobuf_encoding (#2142) Co-authored-by: Max Inden <mail@max-inden.de>
2021-07-28 17:59:08 +02:00
[PR 2142]: https://github.com/libp2p/rust-libp2p/pull/2142
core/: Remove TInEvent and TOutEvent (#2183) TInEvent and TOutEvent are implied through THandler and thus superflucious. Both are removed in favor of a derivation through THandler.
2021-08-11 12:41:28 +02:00
[PR 2137]: https://github.com/libp2p/rust-libp2p/pull/2137
[PR 2183]: https://github.com/libp2p/rust-libp2p/pull/2183
*: Dial with handler and return handler on error and closed (#2191) Require `NetworkBehaviourAction::{DialPeer,DialAddress}` to contain a `ProtocolsHandler`. This allows a behaviour to attach custom state to its handler. The behaviour would no longer need to track this state separately during connection establishment, thus reducing state required in a behaviour. E.g. in the case of `libp2p-kad` the behaviour can include a `GetRecord` request in its handler, or e.g. in the case of `libp2p-request-response` the behaviour can include the first request in the handler. Return `ProtocolsHandler` on connection error and close. This allows a behaviour to extract its custom state previously included in the handler on connection failure and connection closing. E.g. in the case of `libp2p-kad` the behaviour could extract the attached `GetRecord` from the handler of the failed connection and then start another connection attempt with a new handler with the same `GetRecord` or bubble up an error to the user. Co-authored-by: Thomas Eizinger <thomas@eizinger.io>
2021-08-31 17:00:51 +02:00
[PR 2191]: https://github.com/libp2p/rust-libp2p/pull/2191
core/: Remove DisconnectedPeer::set_connected and Pool::add (#2195) This logic seems to be a leftover of https://github.com/libp2p/rust-libp2p/pull/889 and unused today.
2021-08-19 20:17:18 +02:00
[PR 2195]: https://github.com/libp2p/rust-libp2p/pull/2195
protocols/rendezvous: Implement protocol (#2107) Implement the libp2p rendezvous protocol. > A lightweight mechanism for generalized peer discovery. It can be used for bootstrap purposes, real time peer discovery, application specific routing, and so on. Co-authored-by: rishflab <rishflab@hotmail.com> Co-authored-by: Daniel Karzel <daniel@comit.network>
2021-09-08 00:36:52 +10:00
[PR 2107]: https://github.com/libp2p/rust-libp2p/pull/2107
core/: Concurrent dial attempts (#2248) Concurrently dial address candidates within a single dial attempt. Main motivation for this feature is to increase success rate on hole punching (see https://github.com/libp2p/rust-libp2p/issues/1896#issuecomment-885894496 for details). Though, as a nice side effect, as one would expect, it does improve connection establishment time. Cleanups and fixes done along the way: - Merge `pool.rs` and `manager.rs`. - Instead of manually implementing state machines in `task.rs` use `async/await`. - Fix bug where `NetworkBehaviour::inject_connection_closed` is called without a previous `NetworkBehaviour::inject_connection_established` (see https://github.com/libp2p/rust-libp2p/issues/2242). - Return handler to behaviour on incoming connection limit error. Missed in https://github.com/libp2p/rust-libp2p/issues/2242.
2021-10-14 18:05:07 +02:00
[PR 2248]: https://github.com/libp2p/rust-libp2p/pull/2248
core/connection/listeners: Create event on remove_listener (#2261) Create a `ListenersEvent::Closed` when a listener is removed via `Swarm::remove_listener`. This makes it more consistent with `Swarm::listen_on`, and also informs the Swarm about the associated expired addresses. Co-authored-by: Max Inden <mail@max-inden.de>
2021-10-11 22:38:55 +02:00
[PR 2261]: https://github.com/libp2p/rust-libp2p/pull/2261
protocols/rendezvous: Implement protocol (#2107) Implement the libp2p rendezvous protocol. > A lightweight mechanism for generalized peer discovery. It can be used for bootstrap purposes, real time peer discovery, application specific routing, and so on. Co-authored-by: rishflab <rishflab@hotmail.com> Co-authored-by: Daniel Karzel <daniel@comit.network>
2021-09-08 00:36:52 +10:00
[RFC0002]: https://github.com/libp2p/specs/blob/master/RFC/0002-signed-envelopes.md
[RFC0003]: https://github.com/libp2p/specs/blob/master/RFC/0003-routing-records.md
to/into consistency for PublicKey and PeerId (#2145) - Change `PublicKey::into_protobuf_encoding` to `PublicKey::to_protobuf_encoding`. - Change `PublicKey::into_peer_id` to `PublicKey::to_peer_id`. - Change `PeerId::from_public_key(PublicKey)` to `PeerId::from_public_key(&PublicKey)`. - Add `From<&PublicKey> for PeerId`. Co-authored-by: Max Inden <mail@max-inden.de>
2021-07-22 22:34:13 +02:00
*: Prepare v0.39.0 release (#2132)
2021-07-12 21:24:58 +02:00
# 0.29.0 [2021-07-12]
*: Use upstream multiaddr crate (#2075) Use multiaddr instead of parity-multiaddr, removing the latter from the repository.
2021-05-27 14:04:33 +02:00
- Switch from `parity-multiaddr` to upstream `multiaddr`.
build(deps): Update libsecp256k1 requirement from 0.3.1 to 0.5.0 (#2074) * build(deps): Update libsecp256k1 requirement from 0.3.1 to 0.5.0 Updates the requirements on [libsecp256k1](https://github.com/paritytech/libsecp256k1) to permit the latest version. - [Release notes](https://github.com/paritytech/libsecp256k1/releases) - [Changelog](https://github.com/paritytech/libsecp256k1/blob/master/CHANGELOG.md) - [Commits](https://github.com/paritytech/libsecp256k1/commits) Signed-off-by: dependabot[bot] <support@github.com> * core/identity/scp256k1: Use libsecp256k1::SecretKey::random directly * core/: Update changelog and cargo toml Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Max Inden <mail@max-inden.de>
2021-05-21 14:15:51 +02:00
- Update dependencies.
core/CHANGELOG: Add entry for PR 2090 (#2097) Include changelog entry for a24e4221bdeeffc9260e6e08636bc7f8f231e168.
2021-06-08 10:14:31 +02:00
- Implement `Keypair::from_protobuf_encoding` for ed25519 keys (see [PR 2090]).
core/: Redesign `upgrade::{write_one, write_with_len_prefix, read_one}` (#2111) 1. Deprecating the `write_one` function Semantically, this function is a composition of `write_with_len_prefix` and `io.close()`. This represents a footgun because the `close` functionality is not obvious and only mentioned in the docs. Using this function multiple times on a single substream will produces hard to debug behaviour. 2. Deprecating `read_one` and `write_with_len_prefix` functions 3. Introducing `write_length_prefixed` and `read_length_prefixed` - These functions are symmetric and do exactly what you would expect, just writing to the socket without closing - They also have a symmetric interface (no more custom errors, just `io::Error`) Co-authored-by: Max Inden <mail@max-inden.de>
2021-07-04 00:23:10 +10:00
- Deprecate `upgrade::write_one`.
Deprecate `upgrade::write_with_len_prefix`.
Deprecate `upgrade::read_one`.
Introduce `upgrade::read_length_prefixed` and `upgrade::write_length_prefixed`.
See [PR 2111](https://github.com/libp2p/rust-libp2p/pull/2111).
core/CHANGELOG: Add entry for PR 2090 (#2097) Include changelog entry for a24e4221bdeeffc9260e6e08636bc7f8f231e168.
2021-06-08 10:14:31 +02:00
[PR 2090]: https://github.com/libp2p/rust-libp2p/pull/2090
core/src/identity: Fix build with secp256k1 disabled (#2057)
2021-04-26 17:53:50 +03:00
# 0.28.3 [2021-04-26]
*: Rework reporting of invalid and wrong PeerIds (#2441) Previously, the negotiated PeerId was included in the swarm event and inject_dial_failure’s arguments while the expected one was absent. This patch adds the negotiated PeerId to the DialError and includes the expected one in the notifications. Co-authored-by: Roland Kuhn <rk@rkuhn.info>
2022-01-18 21:21:11 +01:00
- Fix build with secp256k1 disabled [PR 2057](https://github.com/libp2p/rust-libp2p/pull/2057).
core/src/identity: Fix build with secp256k1 disabled (#2057)
2021-04-26 17:53:50 +03:00
*: Prepare v0.37.0 release (#2049)
2021-04-13 20:15:15 +02:00
# 0.28.2 [2021-04-13]
core: Update to asn1_der v0.7 (#2000)
2021-03-22 13:53:47 +01:00
- Update dependencies.
core/: Prepare libp2p-core v0.28.1 incl multiaddr v0.11.2 libp2p-dns requires a new feature in parity-multiaddr v0.11.2 namely Multiaddr::ends_with. libp2p-dns does not depend on parity-multiaddr directly but through libp2p-core. Prepare a new version of libp2p-core requiring at least parity-multiaddr v0.11.2 and update libp2p-dns to require libp2p-core v0.28.1.
2021-03-17 16:36:19 +01:00
# 0.28.1 [2021-03-17]
- Update `paritytech-multiaddr` to `>=v0.11.2`.
*: Prepare v0.36.0 release
2021-03-17 15:28:13 +01:00
# 0.28.0 [2021-03-17]
[libp2p-dns] Implement `/dnsaddr` resolution. (#1931) * Implement `/dnsaddr` support on `libp2p-dns`. To that end, since resolving `/dnsaddr` addresses needs "fully qualified" multiaddresses when dialing, i.e. those that end with the `/p2p/...` protocol, we make sure that dialing always uses such fully qualified addresses by appending the `/p2p` protocol as necessary. As a side-effect, this adds support for dialing peers via "fully qualified" addresses, as an alternative to using a `PeerId` together with a `Multiaddr` with or without the `/p2p` protocol. * Adapt libp2p-relay. * Update versions, changelogs and small cleanups.
2021-03-17 10:53:19 +01:00
- `Network::dial()` understands `/p2p` addresses and `Transport::dial`
gets a "fully qualified" `/p2p` address when dialing a specific peer,
whether through the `Network::peer()` API or via `Network::dial()`
with a `/p2p` address.
- `Network::dial()` and `network::Peer::dial()` return a `DialError`
on error.
[core] Shorten and unify Debug impls of public keys. (#1982) * Shorten and unify Debug impls of public keys. ed25519 `PublicKey` and secp256k1 `PublicKey` get a new `Debug` impl, while RSAs `PublicKey` is aligned with the others for uniformity. * Update version and changelog.
2021-03-09 10:56:19 +01:00
- Shorten and unify `Debug` impls of public keys.
Prepare v0.35 (#1957)
2021-02-15 20:06:50 +01:00
# 0.27.1 [2021-02-15]
Update unsigned-varint and asynchronous-codec (#1946) * Update unsigned-varint requirement from 0.6 to 0.7 Updates the requirements on [unsigned-varint](https://github.com/paritytech/unsigned-varint) to permit the latest version. - [Release notes](https://github.com/paritytech/unsigned-varint/releases) - [Changelog](https://github.com/paritytech/unsigned-varint/blob/master/CHANGELOG.md) - [Commits](https://github.com/paritytech/unsigned-varint/compare/v0.6.0...v0.7.0) Signed-off-by: dependabot[bot] <support@github.com> * *: Update to asynchronous-codec v0.6 * transports/plaintext: Use Framed::into_parts * *: Update cargo tomls and changelogs Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Max Inden <mail@max-inden.de>
2021-02-13 20:15:14 +01:00
- Update dependencies.
*: Prepare v0.34.0 release (#1918) Co-authored-by: Roman Borschel <romanb@users.noreply.github.com>
2021-01-12 20:33:43 +01:00
# 0.27.0 [2021-01-12]
*: Switch futures_codec to asynchronous-codec (#1908) `futures-codec` has not been updated in the recent months. It still depends on `bytes` `v0.5` preventing all downstream dependencies to upgrade to `bytes` `v1.0`. This commit replaces `futures_codec` in favor of `asynchronous-codec` The latter is a fully upgraded fork of the former. In addition this commit upgrades: - bytes to v1 - unsigned-varint to v0.6.0 - prost to v0.7
2021-01-12 12:48:37 +01:00
[tcp] Port-reuse, async-io, if-watch (#1887) * Update tomls. * Let transports decide when to translate. * Improve tcp transport. * Update stuff. * Remove background task. Enhance documentation. To avoid spawning a background task and thread within `TcpConfig::new()`, with communication via unbounded channels, a `TcpConfig` now keeps track of the listening addresses for port reuse in an `Arc<RwLock>`. Furthermore, an `IfWatcher` is only used by a `TcpListenStream` if it listens on any interface and directly polls the `IfWatcher` both for initialisation and new events. Includes some documentation and test enhancements. * Reintroduce feature flags for tokio vs async-io. To avoid having an extra reactor thread running for tokio users and to make sure all TCP I/O uses the mio-based tokio reactor. Thereby run tests with both backends. * Add missing files. * Fix docsrs attributes. * Update transports/tcp/src/lib.rs Co-authored-by: Max Inden <mail@max-inden.de> * Restore chat-tokio example. * Forward poll_write_vectored for tokio's AsyncWrite. * Update changelogs. Co-authored-by: David Craven <david@craven.ch> Co-authored-by: Max Inden <mail@max-inden.de>
2021-01-12 13:35:11 +01:00
- (Re)add `Transport::address_translation` to permit transport-specific
translations of observed addresses onto listening addresses.
[PR 1887](https://github.com/libp2p/rust-libp2p/pull/1887)
*: Switch futures_codec to asynchronous-codec (#1908) `futures-codec` has not been updated in the recent months. It still depends on `bytes` `v0.5` preventing all downstream dependencies to upgrade to `bytes` `v1.0`. This commit replaces `futures_codec` in favor of `asynchronous-codec` The latter is a fully upgraded fork of the former. In addition this commit upgrades: - bytes to v1 - unsigned-varint to v0.6.0 - prost to v0.7
2021-01-12 12:48:37 +01:00
- Update dependencies.
*CHANGELOG.md: Prepare v0.33.0 release (#1895)
2020-12-18 10:03:20 +01:00
# 0.26.0 [2020-12-17]
Stack allocated PeerId (#1874) * Stack allocate PeerId. * Update stuff. * Upgrade rusttls to fix build. * Remove unnecessary manual implementations. * Remove PeerId::into_bytes. * Remove bytes dependency. * Perform some cleanup. * Use Into<kbucket::Key<K>>. * Update versions and changelogs. * Fix PR link. * Fix benchmarks. Co-authored-by: Roman S. Borschel <roman@parity.io>
2020-12-15 14:40:39 +01:00
- Make `PeerId` be `Copy`, including small `PeerId` API changes.
[PR 1874](https://github.com/libp2p/rust-libp2p/pull/1874/).
Prepare multistream-select-0.9.1
2020-12-02 16:41:59 +01:00
# 0.25.2 [2020-12-02]
- Require `multistream-select-0.9.1`.
Prepare core-0.25.1 and multiaddr-0.10.
2020-11-25 16:51:07 +01:00
# 0.25.1 [2020-11-25]
- Add missing multiaddr upgrade.
Prepare release of `libp2p-v0.31` and all unreleased sub-crates. (#1857) * Prepare v0.31 * Update core-derive * Update minimum multiaddr patch version in libp2p crate.
2020-11-25 15:30:13 +01:00
# 0.25.0 [2020-11-25]
feat: upgrade multihash (#1792) * feat: upgrade to multihash 0.13 `multihash` changes a lot internally, it is using stack allocation instead of heap allocation. This leads to a few limitations in regards on how `Multihash` can be used. Therefore `PeerId` is now using a `Bytes` internally so that only minimal changes are needed. * Update versions and changelogs. Co-authored-by: Roman Borschel <romanb@users.noreply.github.com> Co-authored-by: Roman S. Borschel <roman@parity.io>
2020-11-17 11:15:20 +01:00
[core/swarm] Refactor and extend configurable connection limits. (#1848) * Refactor and extend configurable connection limits. To better track different connection counts, permit configurable limits for these counts and make these available for inspection efficiently, introduce dedicated connection counters via a `ConnectionCounters` structure that is exposed on the API via the `NetworkInfo`. All connection or connection states that are counted in this way can also have effective configurable limits. * Cleanup * Add missing file. * Refine naming and config API. * Update core/CHANGELOG.md Co-authored-by: Max Inden <mail@max-inden.de> * Update core/CHANGELOG.md Co-authored-by: Max Inden <mail@max-inden.de> Co-authored-by: Max Inden <mail@max-inden.de>
2020-11-23 17:22:15 +01:00
- The `NetworkConfig` API is now a builder that moves `self`.
[PR 1848](https://github.com/libp2p/rust-libp2p/pull/1848/).
- New configurable connection limits for established connections and
dedicated connection counters. Removed the connection limit dedicated
to outgoing pending connection _per peer_. Connection limits are now
represented by `u32` intead of `usize` types.
[PR 1848](https://github.com/libp2p/rust-libp2p/pull/1848/).
feat: upgrade multihash (#1792) * feat: upgrade to multihash 0.13 `multihash` changes a lot internally, it is using stack allocation instead of heap allocation. This leads to a few limitations in regards on how `Multihash` can be used. Therefore `PeerId` is now using a `Bytes` internally so that only minimal changes are needed. * Update versions and changelogs. Co-authored-by: Roman Borschel <romanb@users.noreply.github.com> Co-authored-by: Roman S. Borschel <roman@parity.io>
2020-11-17 11:15:20 +01:00
- Update `multihash`.
[multistream-select] Fix `ls` response encoding/decoding (spec-compliance). (#1811) * Fix ls response encoding/decoding. Thereby remove the now unnecessary arbitrary protocol name length limit. Since it an 'ls' response is always terminated with a dedicated newline (and thus ends with two newlines), an 'ls' response with a single protocol can be disambiguated from a single protocol response by this additional newline. * More commentary * Update versions and changelogs. * Resolve remaining conflict. * Permit empty ls responses, as before.
2020-11-18 12:03:07 +01:00
- Update `multistream-select`.
*: Update changelogs to release v0.30.0 (#1829) * *: Update changelogs to release v0.30.0 * muxers/mplex/CHANGELOG: Reference pull request * misc/multistream-select/CHANGELOG: Update date
2020-11-09 17:46:07 +01:00
# 0.24.0 [2020-11-09]
Remove ConnectionInfo trait (#1813) In all cases, we pass the PeerId directly as the connection info. The flexbility of doing something different here was originally envisioned but turned out to be never needed. For reference see: https://github.com/libp2p/rust-libp2p/issues/1798#issuecomment-714526056 Co-authored-by: Max Inden <mail@max-inden.de>
2020-10-31 01:51:27 +11:00
- Remove `ConnectionInfo` trait and replace it with `PeerId`
everywhere. This was already effectively the case because
`ConnectionInfo` was implemented on `PeerId`.
Prepare v0.29.1 (#1809) * *: Update date in changelogs * core/Cargo.toml: Bump multistream-select to v0.8.4
2020-10-20 17:42:10 +02:00
# 0.23.1 [2020-10-20]
core/Cargo.toml: Update to ed25519-dalek v1.0.1 (#1808)
2020-10-20 17:03:10 +02:00
- Update dependencies.
Prepare release. (#1797)
2020-10-16 20:36:47 +02:00
# 0.23.0 [2020-10-16]
Refine boxing during transport construction. (#1794) * Rework boxing during transport construction. * Cleanup * Fix chat-tokio example. * Update changelogs and versions.
2020-10-16 16:53:02 +02:00
- Rework transport boxing and move timeout configuration
to the transport builder.
[PR 1794](https://github.com/libp2p/rust-libp2p/pull/1794).
Update unsigned-varint requirement from 0.4 to 0.5 (#1761) * Update unsigned-varint requirement from 0.4 to 0.5 Updates the requirements on [unsigned-varint](https://github.com/paritytech/unsigned-varint) to permit the latest version. - [Release notes](https://github.com/paritytech/unsigned-varint/releases) - [Changelog](https://github.com/paritytech/unsigned-varint/blob/master/CHANGELOG.md) - [Commits](https://github.com/paritytech/unsigned-varint/commits/v0.5.1) Signed-off-by: dependabot[bot] <support@github.com> * *: Update changelogs and Cargo tomls Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Max Inden <mail@max-inden.de>
2020-09-16 10:27:33 +02:00
- Update dependencies.
core/Cargo.toml: Require parity-multiaddr 0.9.2 for Ord bound (#1742) With b601ed4 libp2p-core requires the `Ord` bound on `Multiaddr`. This bound is only implemented with parity-multiaddr `0.9.2`. Make sure libp2p-core requires at least parity-multiaddr `0.9.2`. * *: Prepare libp2p 0.28.1 release
2020-09-10 11:03:14 +02:00
# 0.22.1 [2020-09-10]
- Require at least parity-multiaddr v0.9.2 in order to fulfill `Ord` bound on
`Multiaddr`. [PR 1742](https://github.com/libp2p/rust-libp2p/pull/1742).
Prepare release(s). (#1738)
2020-09-09 12:20:25 +02:00
# 0.22.0 [2020-09-09]
Remove temporary peer ID compatibility mode. (#1608) * Remove temporary peer ID compatibility. This removes the temporary compatibility mode between peer IDs using identity hashing and sha256, thus being the last step in the context of https://github.com/libp2p/rust-libp2p/issues/555. * Check digest length in PeerId::from_multihash for Identity hash. * Update core/src/peer_id.rs Co-authored-by: Toralf Wittner <tw@dtex.org> * Update core changelog. * Update core changelog. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-08-26 13:03:35 +02:00
[core] Simplify accepting incoming connections. (#1732) * Simplify incoming connection handling. Instead of handing out a mutable borrow to the connection pool in the `IncomingConnectionEvent`, so one can call `IncomingConnectionEvent::accept()`, just provide `Network::accept()`. * Update docs. * Update CHANGELOG.
2020-09-09 11:21:37 +02:00
- Simplify incoming connection handling. The `IncomingConnectionEvent`
has been removed. Instead, pass the `IncomingConnection` obtained
from `NetworkEvent::IncomingConnection` to `Network::accept()`.
[PR 1732](https://github.com/libp2p/rust-libp2p/pull/1732).
Update core changelog.
2020-09-03 11:29:52 +02:00
- Allow any closure to be passed as an executor.
[PR 1686](https://github.com/libp2p/rust-libp2p/pull/1686)
Remove temporary peer ID compatibility mode. (#1608) * Remove temporary peer ID compatibility. This removes the temporary compatibility mode between peer IDs using identity hashing and sha256, thus being the last step in the context of https://github.com/libp2p/rust-libp2p/issues/555. * Check digest length in PeerId::from_multihash for Identity hash. * Update core/src/peer_id.rs Co-authored-by: Toralf Wittner <tw@dtex.org> * Update core changelog. * Update core changelog. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-08-26 13:03:35 +02:00
- Remove `PeerId` compatibility mode for "identity" and SHA2 hashes.
Historically, before 0.12, `PeerId`s were incorrectly always hashed with SHA2.
Starting from version 0.13, rust-libp2p accepted both hashed and non-hashed keys as
input. Starting from version 0.16 rust-libp2p compared `PeerId`s of "identity" and
SHA2 hashes equal, which made it possible to connect through secio or noise to nodes
with an identity hash for the same peer ID. Starting from version 0.17, rust-libp2p
switched to not hashing the key (i.e. the correct behaviour) while retaining
equality between peer IDs using the "identity" hash and SHA2. Finally, with
this release, that will no longer be the case and it is assumed that peer IDs
whose length is less or equal to 42 bytes always use the "identity" hash so
two peer IDs are equal if and only if they use the same hash algorithm and
have the same hash digest. [PR 1608](https://github.com/libp2p/rust-libp2p/pull/1608).
core/transport/memory: Return dialer address in Upgrade event (#1724) Previously a `Listener` would return its own address as the `remote_addr` in the `ListenerEvent::Upgrade` event. With this commit a `Listener` returns the dialer address as the `remote_addr` in the `ListenerEvent::Upgrade` event. To do so a `DialFuture` registers a port with the global `HUB` at construction which is later on unregistered in the `Drop` implementation of the dialer's `Chan`. The sending side of the `mpsc::channel` registered in the `HUB` is dropped at `DialFuture` construction, thus one can not dial the dialer port. This mimics the TCP transport behaviour preventing both dialing and listening on the same TCP port.
2020-09-08 12:07:15 +02:00
- Return dialer address instead of listener address as `remote_addr` in
`MemoryTransport` `Listener` `ListenerEvent::Upgrade`
[PR 1724](https://github.com/libp2p/rust-libp2p/pull/1724).
*: Prepare v0.24.0 release (#1713) * */CHANGELOG: Update dates * Cargo.toml: Update to 0.24.0
2020-08-18 17:04:34 +02:00
# 0.21.0 [2020-08-18]
[core/swarm] Emit events for active connection close and fix `disconnect()`. (#1619) * Emit events for active connection close and fix `disconnect()`. The `Network` does currently not emit events for actively closed connections, e.g. via `EstablishedConnection::close` or `ConnectedPeer::disconnect()`. As a result, when actively closing connections, there will be `ConnectionEstablished` events emitted without eventually a matching `ConnectionClosed` event. This seems undesirable and has the consequence that the `Swarm::ban_peer_id` feature in `libp2p-swarm` does not result in appropriate calls to `NetworkBehaviour::inject_connection_closed` and `NetworkBehaviour::inject_disconnected`. Furthermore, the `disconnect()` functionality in `libp2p-core` is currently broken as it leaves the `Pool` in an inconsistent state. This commit does the following: 1. When connection background tasks are dropped (i.e. removed from the `Manager`), they always terminate immediately, without attempting an orderly close of the connection. 2. An orderly close is sent to the background task of a connection as a regular command. The background task emits a `Closed` event before terminating. 3. `Pool::disconnect()` removes all connection tasks for the affected peer from the `Manager`, i.e. without an orderly close, thereby also fixing the discovered state inconsistency due to not removing the corresponding entries in the `Pool` itself after removing them from the `Manager`. 4. A new test is added to `libp2p-swarm` that exercises the ban/unban functionality and places assertions on the number and order of calls to the `NetworkBehaviour`. In that context some new testing utilities have been added to `libp2p-swarm`. This addresses https://github.com/libp2p/rust-libp2p/issues/1584. * Update swarm/src/lib.rs Co-authored-by: Toralf Wittner <tw@dtex.org> * Incorporate some review feedback. * Adapt to changes in master. * More verbose panic messages. * Simplify There is no need for a `StartClose` future. * Fix doc links. * Further small cleanup. * Update CHANGELOGs and versions. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-08-04 11:30:09 +02:00
Update core changelog.
2020-08-24 10:48:36 +02:00
- Remove duplicates when performing address translation
[PR 1697](https://github.com/libp2p/rust-libp2p/pull/1697).
Changelog updates.
2020-08-17 10:14:44 +02:00
- Add `transport::Builder::multiplex_ext` for further customisation during
`StreamMuxer` creation. [PR 1691](https://github.com/libp2p/rust-libp2p/pull/1691).
[core/swarm] Emit events for active connection close and fix `disconnect()`. (#1619) * Emit events for active connection close and fix `disconnect()`. The `Network` does currently not emit events for actively closed connections, e.g. via `EstablishedConnection::close` or `ConnectedPeer::disconnect()`. As a result, when actively closing connections, there will be `ConnectionEstablished` events emitted without eventually a matching `ConnectionClosed` event. This seems undesirable and has the consequence that the `Swarm::ban_peer_id` feature in `libp2p-swarm` does not result in appropriate calls to `NetworkBehaviour::inject_connection_closed` and `NetworkBehaviour::inject_disconnected`. Furthermore, the `disconnect()` functionality in `libp2p-core` is currently broken as it leaves the `Pool` in an inconsistent state. This commit does the following: 1. When connection background tasks are dropped (i.e. removed from the `Manager`), they always terminate immediately, without attempting an orderly close of the connection. 2. An orderly close is sent to the background task of a connection as a regular command. The background task emits a `Closed` event before terminating. 3. `Pool::disconnect()` removes all connection tasks for the affected peer from the `Manager`, i.e. without an orderly close, thereby also fixing the discovered state inconsistency due to not removing the corresponding entries in the `Pool` itself after removing them from the `Manager`. 4. A new test is added to `libp2p-swarm` that exercises the ban/unban functionality and places assertions on the number and order of calls to the `NetworkBehaviour`. In that context some new testing utilities have been added to `libp2p-swarm`. This addresses https://github.com/libp2p/rust-libp2p/issues/1584. * Update swarm/src/lib.rs Co-authored-by: Toralf Wittner <tw@dtex.org> * Incorporate some review feedback. * Adapt to changes in master. * More verbose panic messages. * Simplify There is no need for a `StartClose` future. * Fix doc links. * Further small cleanup. * Update CHANGELOGs and versions. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-08-04 11:30:09 +02:00
- Refactoring of connection close and disconnect behaviour. In particular, the former
`NetworkEvent::ConnectionError` is now `NetworkEvent::ConnectionClosed` with the `error`
field being an `Option` and `None` indicating an active (but not necessarily orderly) close.
This guarantees that `ConnectionEstablished` events are always eventually paired
with `ConnectionClosed` events, regardless of how connections are closed.
Correspondingly, `EstablishedConnection::close` is now `EstablishedConnection::start_close`
to reflect that an orderly close completes asynchronously in the background, with the
outcome observed by continued polling of the `Network`. In contrast, `disconnect`ing
a peer takes effect immediately without an orderly connection shutdown.
See [PR 1619](https://github.com/libp2p/rust-libp2p/pull/1619) for further details.
protocols/kad: Implement NetworkBehaviour::inject_address_change (#1649) With 826f513 a `StreamMuxer` can notify that the address of a remote peer changed. This is needed to support the transport protocol QUIC as remotes can change their IP addresses within the lifetime of a single connection. This commit implements the `NetworkBehaviour::inject_address_change` handler to update the Kademlia routing table accordingly.
2020-08-06 15:35:24 +02:00
- Add `ConnectedPoint::get_remote_address`
([PR 1649](https://github.com/libp2p/rust-libp2p/pull/1649)).
[core]: fix typo in CHANGELOG.md (#1688)
2020-08-04 23:13:38 +02:00
# 0.20.1 [2020-07-17]
Upgrade ed25519-dalek to pre.4 (#1665) * Upgrade ed25519-dalek to pre.4 * Update core/src/identity/ed25519.rs Co-authored-by: Pierre Krieger <pierre.krieger1708@gmail.com> Co-authored-by: Pierre Krieger <pierre.krieger1708@gmail.com>
2020-07-17 12:01:49 +02:00
- Update ed25519-dalek dependency.
Prepare releases. (#1640) * Prepare releases. * Re-export libp2p-request-response from libp2p crate. * Clean up changelogs. * Restore upper bounds. * Version 0.21 for the root crate. * Stricter lower bound in libp2p-websocket version in root crate. * Update misc/peer-id-generator/Cargo.toml Co-authored-by: Toralf Wittner <tw@dtex.org> * Update release date. * Update misc/peer-id-generator/Cargo.toml Co-authored-by: Toralf Wittner <tw@dtex.org> Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-07-01 15:36:20 +02:00
# 0.20.0 [2020-07-01]
- Conditional compilation fixes for the `wasm32-wasi` target
([PR 1633](https://github.com/libp2p/rust-libp2p/pull/1633)).
Allow StreamMuxer to notify changes in the address (#1621) * Allow StreamMuxer to notify changes in the address * Fix doc link * Revert accidental rename * Other accidental rename Co-authored-by: Roman Borschel <romanb@users.noreply.github.com>
2020-06-30 17:10:53 +02:00
- Rename `StreamMuxer::poll_inbound` to `poll_event` and change the
return value to `StreamMuxerEvent`. This new `StreamMuxerEvent` makes
it possible for the multiplexing layer to notify the upper layers of
a change in the address of the underlying connection.
- Add `ConnectionHandler::inject_address_change`.
Prepare release. (#1620)
2020-06-22 11:41:28 +02:00
# 0.19.2 [2020-06-22]
- Add PartialOrd and Ord for PeerId
([PR 1594](https://github.com/libp2p/rust-libp2p/pull/1594)).
- Updated dependencies.
- Deprecate `StreamMuxer::is_remote_acknowledged`
([PR 1616](https://github.com/libp2p/rust-libp2p/pull/1616)).
Reference in New Issue Copy Permalink