Updated CHANGELOG.md files

Author: coot

cardano-client/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 ## next version
 
+### Breaking changes
+
+* Reimplemntation of `subscribe` without relaying on non-p2p stack.  Its
+  arguments have changed.  Note that the `NodeToClientProtocols` and
+  `OuroborosApplicationWithMinimalCtx` specify `Void` as return type of the
+  responder side.
+* The default reconnect delay was increased from `0.025s` to `5s`.
+
+### Non-breaking changes
+
 ## 0.3.1.5 -- 2024-08-27
 
 ### Breaking changes

network-mux/CHANGELOG.md

@@ -9,6 +9,10 @@
 * `Ouroboros.Network.Mux.mkMiniProtocolBundle` was renamed to
   `mkMiniProtocolInfos`, its type changed.
 * Removed `MiniProtocolBundle` newtype wrapper.
+* Generalised `Channel` type and provide `ByteChannel` type alias.
+* Provide additional APIs in the `Network.Mux.Channel` for creating channels
+  and byte channels.
+* `MuxBearer` has a `name` field.
 
 ### Non-breaking changes
 

ouroboros-network-framework/CHANGELOG.md

@@ -10,6 +10,12 @@
 * Renamed `Ouroboros.Network.Mux.mkMiniProtocolBundle` as `mkMiniProtocolInfos`
   (its type has changed).
 * Added `Ouroboros.Network.Mux.toMiniProtocolInfos`.
+* Added `ConnectToArgs` for `Ouroboros.Network.Socket.connectToNode` & friends.
+* `Ouroboros.Network.Socket.connectToNode` & friends return result (or an
+  error) of the first terminated mini-protocol.
+* Added `Ouroboros.Network.Socket.connectToNodeWithMux` and
+  `connectToNodeWithMux'`.  They give control over running mux, e.g. one can
+  start some of the mini-protocols, or implement a re-start policy.
 
 ### Non-breaking changes
 

ouroboros-network/CHANGELOG.md

@@ -24,6 +24,14 @@
   It is used by `outboundConnectionsState` when signaling trust state when syncing in
   Genesis mode. Default value is provided by the Configuration module.
 * Using `typed-protocols-0.2.0.0`.
+* `Ouroboros.Network.NodeToClient.connectTo` takes
+  `OuroborosApplicationWithMinimalCtx` which is using `Void` type for responder
+  protocols.  It anyway only accepts `InitiatorMode`, and thus no responder
+  protocols can be specified, nontheless this might require changing type
+  signature of the applications passed to it.  `connectTo` returns now either
+  an error or the result of the first terminated mini-protocol.
+* `Ouroboros.Network.NodeToNode.connectTo` returns either an error or the
+  result of the first terminated mini-protocol.
 
 ### Non-Breaking changes