⚡️ 0.24 RELEASE 🚀 #249
Assignees
Comments
jacobheun
added
status/in-progress
|
Release Candidate 0.24.0-rc.1 has been published to npm and can be installed via |
|
What's the ETA on this one? |
|
I'm fixing some issues with the examples and working on a dependency issue with |
Merged
|
Release candidate 0.24.0-rc.3 has been published to npm and can be installed via |
|
0.24 is out! https://ipfs.io/blog/55-js-libp2p-0-24/ |
ghost
removed
the
|
@jacobheun @vasco-santos mind following up with agoric-labs/PlaygroundVat#8 given that the 0.24 released happened? :) |
maschad
pushed a commit
to maschad/js-libp2p
that referenced
this issue
Jun 21, 2023
This was incorrectly logging as a timeout when it should be logging a close. Also updates end event log for consistency with the other logging.
maschad
pushed a commit
to maschad/js-libp2p
that referenced
this issue
Jun 21, 2023
## [6.1.1](libp2p/js-libp2p-tcp@v6.1.0...v6.1.1) (2023-01-26) ### Bug Fixes * update log message when socket closes ([libp2p#249](libp2p/js-libp2p-tcp#249)) ([f95bbf1](libp2p/js-libp2p-tcp@f95bbf1))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🗺 What's left for release
🔦 Highlights
🚦 Custom Content/Peer Routing Support
Libp2p will now support custom content and peer routers, which will enable users to better customize their DHT experience. The new release allows for using the new Delegated Peer Routing and Delegated Content Routing modules to leverage an external nodes DHT instead of or in conjunction with their own. This enables nodes in more resource restricted environments to use an external DHT instead of running their own, which can be very resource intensive.
🔌 Relay enabled by default
In an effort to improve default connectivity, circuit relay is now enabled by default. Hop is still disabled by default to prevent relaying traffic for other nodes out of the box, as this is expensive for the node. By enabling circuit relay by default, nodes will now be able to accept and dial to other circuit relay nodes. This improves a nodes default ability to communicate in isolated environments.
🤖 State Machine
Libp2p is now a state machine. When starting and stopping the node you can now listen for the
stopandstartevents. Libp2p also exposes a new method,dialFSM, which calls back with a Connection State Machine. This gives users the ability to listen to more events on individual connections. You can find out more about these events in libp2p-switch readme.🏗 API Changes
dialFSM(peer, protocol, callback)which allows users to hook into more connection level activity. You can read more about in the readme.startandstopevents on node start and stop respectively..start()and.stop()are now optional. You can instead listen to theerror,start, andstopevents.✅ Release Checklist
🙌🏽 Want to contribute?
Would you like to contribute to the libp2p project and don't know how? Well, there are a few places you can get started:
help wantedlabel at the Ready column in our waffle board - https://waffle.io/libp2p/js-libp2p?label=help%20wantedThe best place to ask your questions about libp2p, how it works and what you can do with it is at discuss.ipfs.io. We are also available at the #libp2p channel on Freenode.
The text was updated successfully, but these errors were encountered: