6 Commits

Author	SHA1	Message	Date
Thomas Eizinger	5df321d8b9	fix(allowblocklist): correctly remove Peer from sets ... Previously, we reinserted the `Peer` in the "undo" function which is obviously wrong. This patch fixes the behaviour to be correct and adds two regression tests. Pull-Request: #3789.	2023-04-19 15:51:20 +00:00
Thomas Eizinger	451c64a8b8	fix: specify correct libp2p-swarm dependency ... With https://github.com/libp2p/rust-libp2p/pull/3658, these crates depend on the `0.42.1` release to access the new `ToSwarm` type. With the currently specified version, a user could theoretically run into a compile error if they pin `libp2p-swarm` to `0.42.0` in their lockfile but update to the latest patch release of one of these crates. Pull-Request: #3711.	2023-04-05 19:44:32 +00:00
Max Inden	d7396706d0	fix(changelog): Make release heading levels consistent ... See `##` for release headings everywhere. This is consistent with markdown conventions of one `#` per document and in line with https://keepachangelog.com/. See report in https://github.com/libp2p/rust-libp2p/issues/3531. Pull-Request: #3561.	2023-03-30 21:04:01 +00:00
Max Inden	486ac8baf2	chore: prepare libp2p v0.51.2 ... Depends-On: #3693. Pull-Request: #3694.	2023-03-29 13:04:18 +00:00
Thomas Eizinger	dcbc04e89e	feat(swarm): rename NetworkBehaviourAction to ToSwarm ... Resolves #3123. Pull-Request: #3658.	2023-03-24 13:43:49 +00:00
Thomas Eizinger	f64187049d	feat: introduce libp2p-allow-block-list connection management module ... Currently, banning peers is a first-class feature of `Swarm`. With the new connection management capabilities of `NetworkBehaviour`, we can now implement allow and block lists as a separate module. We introduce a new crate `libp2p-allow-block-list` and deprecate `Swarm::ban_peer_id` in favor of that. Related #2824. Pull-Request: #3590.	2023-03-21 20:58:09 +00:00