Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Release litep2p 0.9.1 #328

Merged
merged 3 commits into from
Feb 20, 2025
Merged

chore: Release litep2p 0.9.1 #328

merged 3 commits into from
Feb 20, 2025

Conversation

lexnv
Copy link
Collaborator

@lexnv lexnv commented Feb 19, 2025

[0.9.1] - 2025-01-19

This release enhances compatibility between litep2p and libp2p by backporting the latest Yamux updates. Additionally, it includes various improvements and fixes to boost the stability and performance of the WebSocket stream and the multistream-select protocol.

Changed

  • yamux: Switch to upstream implementation while keeping the controller API (#320)
  • req-resp: Replace SubstreamSet with FuturesStream (#321)
  • cargo: Bring up to date multiple dependencies (#324)
  • build(deps): bump hickory-proto from 0.24.1 to 0.24.3 (#323)
  • build(deps): bump openssl from 0.10.66 to 0.10.70 (#322)

Fixed

  • websocket/stream: Fix unexpected EOF on Poll::Pending state poisoning (#327)
  • websocket/stream: Avoid memory allocations on flushing (#325)
  • multistream-select: Enforce io::error instead of empty protocols (#318)
  • multistream: Do not wait for negotiation in poll_close (#319)

cc @paritytech/networking

Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
@lexnv lexnv self-assigned this Feb 19, 2025
Signed-off-by: Alexandru Vasile <alexandru.vasile@parity.io>
@lexnv lexnv merged commit 2a49fd0 into master Feb 20, 2025
8 checks passed
@lexnv lexnv deleted the lexnv/release-0.9.1 branch February 20, 2025 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants