Updated CHANGELOG.md files

Author: coot

typed-protocols-cborg/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Revision history for typed-protocols-cborg
 
+## 0.3.0.0
+
+* bumped version to agree with `typed-protocols-stateful-0.3.0.0`
+
+## 0.2.0.0
+
+* updated to use `typed-protocols-0.2.0.0`
+
 ## 0.1.0.0 -- 2021-07-28
 
 * Initial experiments and prototyping

typed-protocols-stateful-cborg/CHANGELOG.md

@@ -0,0 +1,12 @@
+# Revision history of typed-protocols-stateful
+
+## 0.3.0.0
+
+* bumped version to agree with `typed-protocols-stateful-0.3.0.0`, in particular:
+  when encoding the local state associated to the initial message state is
+  passed to the codec.
+
+## 0.2.0.0
+
+* Initial version
+

typed-protocols-stateful-cborg/ChangeLog.md

@@ -1,6 +1,12 @@
-# Revision history for typed-protocols-cborg
+# Revision history for typed-protocols-stateful-cborg
 
-## 0.1.0.0 -- 2021-07-28
+## 0.3.0.0
 
-* Initial experiments and prototyping
+* bumped version to agree with `typed-protocols-stateful-0.3.0.0`, in particular:
+  when encoding the local state associated to the initial message state is
+  passed to the codec.
+
+## 0.2.0.0
+
+* Initial version
 

typed-protocols-stateful-cborg/typed-protocols-stateful-cborg.cabal

@@ -14,7 +14,7 @@ category:            Control
 build-type:          Simple
 
 -- These should probably be added at some point.
-extra-source-files:  ChangeLog.md, README.md
+extra-source-files:  CHANGELOG.md, README.md
 
 library
   exposed-modules:   Network.TypedProtocol.Stateful.Codec.CBOR

typed-protocols-stateful/CHANGELOG.md

@@ -0,0 +1,20 @@
+# Revision history of typed-protocols-stateful
+
+## 0.3.0.0
+
+* when encoding a message the local state associated to the initial message
+  state, rather than final state, is passed to the codec. For that reason:
+  * `Yield` requires local state associated to both the initial and final protocol state
+  *  `Codec` and `Driver` have changed accordingly
+
+  This change eliminates the need to have add extra fields in messages which
+  are not send over the wire, see the `Network.TypedProtocol.Stateful.ReqResp`
+  example.
+* `AnyMessage` takes only the local state associated to the initial protocol state of the `Message`.
+* Removed `Show` instance of `AnyMessage`, provided instead `showAnyMessage`.
+* `AnyMessageWithAgency` pattern synonym is exported as a constructor of `AnyMessage`.
+* constraints of `prop_*` APIs where changed.
+
+## 0.2.0.0
+
+* Initial version

typed-protocols-stateful/typed-protocols-stateful.cabal

@@ -12,6 +12,7 @@ author:              Marcin Szamotulski
 maintainer:          [email protected]
 category:            Control
 build-type:          Simple
+extra-source-files:  CHANGELOG.md
 
 -- These should probably be added at some point.
 -- extra-source-files:  ChangeLog.md, README.md

typed-protocols/CHANGELOG.md

@@ -1,11 +1,28 @@
 # Revision history for typed-protocols
 
-## [Unreleased]
-
-- A major redesign of `typed-protocols`.  `Protocol` class requires data family
-  `Message` and new associated type familiy instance `StateAgency`.  One also
-  needs to define singletons and `Sing` & `SingI` instances from the
-  [`singletons`][singletons-3.0.1] package.
+## 0.3.0.0
+
+* `AnyMessageWithAgency` pattern synonym is exported as a constructor of `AnyMessage`.
+* Bumped version to agree with `typed-protocols-stateful`.
+
+## 0.2.0.0
+
+* A major redesign of `typed-protocols`.
+  * `Protocol` class does not require to provide proof obligations for agancy.
+    Proofs are now provided by the framework for all protocols. Agency is now
+    provided by an associated type family `StateAgency`, and evidence for it,
+    in form of a singleton, by `StateToken` type family
+    (similar to `Sing` from the `singletons` package).
+  * `Peer` takes a different evidence type for agency,
+    `Network.TypedProtocol.Peer.{Client,Server}` modules provide pattern synonyms
+     which provide agency evidence and thus are easier to use.
+  * One `Peer` is provided for both non- and pipelined protocol evolution.
+    An extra parameter is added of kind `IsPipelined`. As a result
+    `Outstanding` is now a type family rather than a type alias.
+  * `ActiveAgency` type class is used to distinguish states in which one side
+    has an agency (e.g. the protocol hasn't yet terminated), `nonActiveState` can
+    be used in the same way as `Data.Void.absurd` - which is useful when writing
+    codecs.
 
 ## 0.1.1.1
 * unbuildable (with `base < 0` constraint in CHaP); We cannot support