docs(changelog): boxo and go-libp2p

docs/changelogs/v0.30.md

@@ -6,6 +6,8 @@
 
 - [Overview](#overview)
 - [🔦 Highlights](#-highlights)
+  - [Improved P2P connectivity](#improved-p2p-connectivity)
+  - [Refactored Bitswap and dag-pb chunker](#refactored-bitswap-and-dag-pb-chunker)
   - [WebRTC-Direct Transport enabled by default](#webrtc-direct-transport-enabled-by-default)
   - [AutoNAT V2 Service Introduced Alongside V1](#autonat-v2-service-introduced-alongside-v1)
   - [Automated `ipfs version check`](#automated-ipfs-version-check)
@@ -21,6 +23,26 @@
 
 ### 🔦 Highlights
 
+This release took longer and is more packed with fixes and features than usual.
+
+> [!IMPORTANT]
+> TLDR: update, it contains many, many fixes.
+
+#### Improved P2P connectivity
+
+This release comes with significant go-libp2p update from v0.34.1 to v0.36.3 ([release notes](https://github.com/ipfs/boxo/releases/)).
+
+It includes multiple fixes to key protocols: QUIC/Webtransport/WebRTC, Connection Upgrades through Relay ([DCUtR](https://github.com/libp2p/specs/blob/master/relay/DCUtR.md)), and Secure WebSockets. 
+
+Also, peers that are behind certain types of NAT will now be more reachable. For this alone, Kubo users are highly encouraged to upgrade.
+
+#### Refactored Bitswap and dag-pb chunker
+
+Some workloads may experience improved memory profile thanks to optimizations from Boxo SDK [v0.23.0](https://github.com/ipfs/boxo/releases/tag/v0.23.0).
+
+> [!IMPORTANT]
+> Storage providers should upgrade to take advantage of the Bitswap server fix, which resolves the issue of greedy peers depleting available wantlist slots for their PeerID, resulting in stalled downloads.
+
 #### WebRTC-Direct Transport enabled by default
 
 Kubo now ships with `/udp/4001/webrtc-direct` listener enabled by default.