You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CHANGELOG.md
+13-12
Original file line number
Diff line number
Diff line change
@@ -9,17 +9,29 @@ As a minor extension, we also keep a semantic version for the `UNRELEASED`
9
9
changes.
10
10
11
11
12
-
## [0.16.0] - UNRELEASED
12
+
## [0.16.0] - 2024-04-03
13
13
14
14
- Tested with `cardano-node 8.9.0`, `cardano-cli 8.20.3.0` and `mithril 2412.0`.
15
15
16
+
-**BREAKING** Change to the `hydra-node` logs, monitoring and removal of `log-filter` executable:
17
+
- Renamed the `Event` data types to `Input` and consequently log items like `BeginEvent` to `BeginInput`.
18
+
- Changed structure of `LogicOutcome` entries.
19
+
- Added node-level log entry when an input was `DroppedFromQueue`.
20
+
- In course of this, the `log-filter` executable was removed as nobody is actively using it and other off-the-shelf utilities to manipulate structured JSON logs (`jq` is already quite powerful) are recommended.
-**BREAKING** Hydra scripts changed due to updates in the `plutus` toolchain:
17
24
- Overall slight increase in script size.
18
25
- 50% less memory usage in `close` and `contest` transactions.
19
26
- Slightly less memory usage in `abort` and may be possible with 6 parties now.
20
27
21
28
-**BREAKING** Transaction serialization on hydra-node api and persisted data changed.
22
29
30
+
- Introduce `EventSource` and `EventSink` interfaces in `hydra-node`:
31
+
- These handles can now be used as "extension points" to make the `hydra-node` store and load its state differently or expose `StateEvent`s to other, external services.
32
+
- Internal refactoring of persistence mechanism as event source and sink in a backward-compatible way.
33
+
- More details can be found in [ADR21](https://hydra.family/head-protocol/adr/21/)
34
+
23
35
- Add metadata to identify Hydra protocol transactions created by `hydra-node`.
24
36
25
37
- Provide more details about why a command failed. Added the state of the head logic at the point of failure.
-**BREAKING** Change to the `hydra-node` logs, monitoring and removal of `log-filter` executable:
44
-
- Renamed the `Event` data types to `Input` and consequently log items like `BeginEvent` to `BeginInput`.
45
-
- Changed structure of `LogicOutcome` entries.
46
-
- Added node-level log entry when an input was `DroppedFromQueue`.
47
-
- In course of this, the `log-filter` executable was removed as nobody is actively using it and other off-the-shelf utilities to manipulate structured JSON logs (`jq` is already quite powerful) are recommended.
- Introduce `EventSource` and `EventSink` interfaces in `hydra-node`:
51
-
- These handles can now be used as "extension points" to make the `hydra-node` store and load its state differently or expose `StateEvent`s to other, external services.
52
-
- Internal refactoring of persistence mechanism as event source and sink in a backward-compatible way.
53
-
- More details can be found in [ADR21](https://hydra.family/head-protocol/adr/21/)
0 commit comments