chore: release 0.38.0

[github-actions[bot]]

:robot: I have created a release *beep* *boop*

0.38.0 (2022-08-12)

⚠ BREAKING CHANGES

• Streams are now Duplex<Uint8ArrayList, Uint8ArrayList | Uint8Array>
• connectionManager.peerValue has been removed, use peerStore.tagPeer instead
• limit protocol streams per-connection (#1255)
• uses new single-issue libp2p interface modules

Features

• limit protocol streams per-connection (#1255) (de30c2c)
• programmatically set agentVersion for use in identify (#1296) (0bb1b80), closes #686 #1240
• update libp2p interfaces (#1252) (d4dd664)
• use tag values to choose which connections to close (#1276) (b1b2b21)

Bug Fixes

• add successful stream peer to protobook (#1341) (8880eef)
• add timeout for circuit relay (#1294) (ba56c64)
• add timeout for incoming connections and build-in protocols (#1292) (750ed9c)
• close streams when protocol limits are reached (#1301) (3c0fb13)
• MaxListenersExceeded warning (#1297) (627b8bf)
• remove mplex prefix from muxer errors (#1304) (05e8e7e)
• specify max stream args separately (#1254) (5371729)
• update muxer behavior (#1289) (b1b9139)
• use keep-alive tag to reconnect to peers on startup (#1278) (2836acc)

deps

• update all deps to support no-copy operations (#1335) (f439d9b)

---

This PR was generated with Release Please. See documentation.

[D4nte]

@achingbrain, any chance we could get the release please? This contains few bug fixes I'd love to get :) https://github.com/ChainSafe/js-libp2p-gossipsub/issues/305 and https://github.com/libp2p/js-libp2p-mplex/issues/191

[achingbrain]

@D4nte soon! I'm just treading carefully around some of the protocol stream limiting stuff as it will cause things to break if the limits are not set correctly.

Can you please try out the RC with npm i libp2p@next and report back any breakage?

[D4nte]

@D4nte soon! I'm just treading carefully around some of the protocol stream limiting stuff as it will cause things to break if the limits are not set correctly.

Can you please try out the RC with npm i libp2p@next and report back any breakage?

I have actually been using master locally and yes, I found an issue with protocol stream limits and libp2p-gossipsub. I haven't had the time to write up an issue or PR yet.

In short, the outbound limit is being reached and throwing an error when connecting to a new peer because gossipsub tries to open an outbound stream.

This is because an outbound stream already exists but gossipsub class isn't aware of it. I guess libp2p opens the stream upon dial.

I was going to write a fix in gossipsub to check existing stream on libp2p and register it before trying to open

Will provide more details soon.

[D4nte]

The issue I was referring to: https://github.com/ChainSafe/js-libp2p-gossipsub/issues/306

[wemeetagain]

:tada: congrats @achingbrain

[github-actions[bot]]

:robot: Release is at https://github.com/libp2p/js-libp2p/releases/tag/v0.38.0 :sunflower: