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
Resolves#2170
<!-- Describe your change here -->
---
<!-- Consider each and tick it off one way or the other -->
* [ ] CHANGELOG updated or not needed
* [ ] Documentation updated or not needed
* [ ] Haddocks updated or not needed
* [ ] No new TODOs introduced or explained herafter
Copy file name to clipboardExpand all lines: CHANGELOG.md
+35-4Lines changed: 35 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,10 +8,41 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
8
8
As a minor extension, we also keep a semantic version for the `UNRELEASED`
9
9
changes.
10
10
11
-
## [0.23.0] - UNRELEASED
11
+
## [0.22.4] - 2025-08-05
12
12
13
13
- Accept additional field `amount` when depositing to specify the amount of Lovelace that should be depositted to a Head returning any leftover to the user.
14
14
15
+
- Fix API not correctly handling event log rotation. This was evident in not
16
+
being able to use `/commit` although the head is initializing or outdated
17
+
information in the `Greetings` message.
18
+
19
+
- Ignore snapshot signatures of already confirmed snapshots. This was previously
20
+
resulting in the node waiting for the accompanying snapshot request and
21
+
occurred when running heads with mirror nodes.
22
+
23
+
- Fix an internal persistent queue blocking after restart when it reached
24
+
capacity.
25
+
26
+
- Timeout and retry broadcast of network messages after 3 seconds in case the
27
+
`etcd` grpc server is not responsive. This should avoid build-up on the
28
+
outbound persistent queue.
29
+
30
+
- Handle failing lease keep alive in network component and avoid bursts in
31
+
heartbeating.
32
+
33
+
- Fix for blocking bug when broadcasting messages via etcd. See:
34
+
https://github.com/cardano-scaling/hydra/issues/2167. This is not a full fix
35
+
but is enough to resolve the problem until we can identify the central cause
36
+
of the issue.
37
+
38
+
## [0.22.3] - 2025-07-21
39
+
40
+
* Change behavior of `Hydra.Network.Etcd` to fallback to earliest possible
41
+
revision if `last-known-revision` is missing or too old. This can happen if a
42
+
node is down for a long time and the `etcd` cluster compacted the last known
0 commit comments