rust-libp2p/misc/allow-block-list/CHANGELOG.md

## 0.1.1

- Correctly unblock and disallow peer in `unblock_peer` and `disallow_peer` functions.
  See [PR 3789].

[PR 3789]: https://github.com/libp2p/rust-libp2p/pull/3789

## 0.1.0

- Initial release.
chore: prepare patch releases on top of v0.51.3 Note that this does not release v0.51.4, i.e. there is no patch release of the meta crate `libp2p`. Pull-Request: #3854. 2023-05-01 04:56:32 +02:00			`## 0.1.1`
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 17:51:20 +02:00
			- Correctly unblock and disallow peer in `unblock_peer` and `disallow_peer` functions.
			`See [PR 3789].`

			`[PR 3789]: https://github.com/libp2p/rust-libp2p/pull/3789`

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 23:04:01 +02:00			`## 0.1.0`
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 21:58:09 +01:00
			`- Initial release.`