@blinklabs/dingo 0.27.3 → 0.27.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/RELEASE_NOTES.md +81 -0
  2. package/package.json +1 -1
package/RELEASE_NOTES.md CHANGED
@@ -1,6 +1,87 @@
1
1
  # Release Notes
2
2
 
3
3
 
4
+ ## v0.27.4 (March 18, 2026)
5
+
6
+ **Title:** Reliability and usability refinements
7
+
8
+ **Date:** March 18, 2026
9
+
10
+ **Version:** v0.27.4
11
+
12
+ Hi folks! Here’s what we shipped in v0.27.4.
13
+
14
+ ### ✨ What's New
15
+
16
+ - **Rock-solid chain-sync recovery:** Sync stays more rock-solid because chain-sync recovers more reliably from stalled or unstable network connections.
17
+ - **Solid chain selection:** Sync wastes less time on poor candidates because chain selection now takes peer suitability into account.
18
+
19
+ ### 💪 Improvements
20
+
21
+ - **Simpler config loading:** Configuration stays under your control because config loading no longer fills in a default Cardano configuration path.
22
+ - **Sleeker block downloads:** Block downloads are more consistent because header processing no longer gets blocked by duplicate headers.
23
+ - **More robust intersections:** Synchronization starts from the right place more often because intersection point selection is now more robust.
24
+
25
+ ### 🔧 Fixes
26
+
27
+ - **No missing boundary blocks:** Historical imports are more complete because older-era boundary blocks are no longer skipped during block loading.
28
+
29
+ ### 📋 What You Need to Know
30
+
31
+ - **Inbound peers excluded from chain choice:** Chain selection behavior may change in mixed inbound/outbound topologies because inbound peers no longer influence which chain is selected.
32
+ - **Documentation-only change:** This release includes a release-notes update with no runtime impact.
33
+
34
+ ### 🙏 Thank You
35
+
36
+ Thank you for trying!
37
+
38
+ ---
39
+
40
+ ## v0.27.3 (March 17, 2026)
41
+
42
+ **Title:** Safer rollbacks and steadier leader election
43
+
44
+ **Date:** March 17, 2026
45
+
46
+ **Version:** v0.27.3
47
+
48
+ Hi folks! Here’s what we shipped in v0.27.3.
49
+
50
+ ### ✨ What's New
51
+
52
+ - **Follow-tip reset and rollback:** Tip tracking is easier to manage because the follow-tip API now supports safe reset and rollback with clearer metadata about what changed.
53
+ - **Leader election readiness:** Block producer readiness is easier to track because leader election now surfaces epoch-nonce readiness and carries schedule state more reliably across restarts.
54
+
55
+ ### 💪 Improvements
56
+
57
+ - **More consistent cache sizing:** Sizing runs are easier to tune because cache defaults are more consistent and the BP/PI sizing script now supports explicit memory limits and optional cache overrides.
58
+ - **Predictable KES period semantics:** Operational certificate (KES) periods are more predictable because KES endpoints now standardize on absolute periods while translating internally from the certificate start period.
59
+ - **Preserved original block bytes:** Downstream tooling can retain exact block bytes because API block objects now include the original encoded bytes.
60
+ - **Standard network identifiers from genesis:** Network identification is simpler because genesis reads now return a standard CAIP-2 network identifier derived from network magic.
61
+ - **Smoother peer switching:** Sync stays more rock-solid because chain-sync now preserves its state while only swapping the active connection during a peer switch.
62
+ - **More consistent Mithril imports:** Mithril snapshot imports are more consistent across epochs because imports now normalize snapshot types and centralize persistence and epoch-summary handling.
63
+ - **Protocol dependency validation:** Modern-era transaction handling is more reliable because protocol dependencies were updated and regression tests now guard transaction size behavior.
64
+ - **Safer default containers:** Default containers are safer because the main Docker image now runs as a non-root `dingo` user.
65
+
66
+ ### 🔧 Fixes
67
+
68
+ - **Resilient background monitoring:** Long-running monitoring is more rock-solid because the stall checker now recovers from panics instead of crashing its background loop.
69
+ - **Robust block fetch batching:** Block fetch serving is more robust because batching now handles iterator errors and connection closes correctly.
70
+ - **Clearer unexpected event handling:** Event processing is easier to debug because chain-sync and block fetch now log unexpected event payload types instead of failing silently.
71
+ - **Reliable shutdown error reporting:** Shutdowns are easier to troubleshoot because node and metrics server shutdown now propagates errors instead of exiting abruptly.
72
+ - **Clear tx-submission failures:** Transaction submission fails more clearly because the tx-submission handlers now return an explicit error when no mempool consumer exists.
73
+
74
+ ### 📋 What You Need to Know
75
+
76
+ - **Docker volume permissions:** If you run Dingo in Docker with mounted volumes, make sure the data directory is writable by the `dingo` user inside the container.
77
+ - **API integrations:** If you integrate with follow-tip or KES APIs, give your client code a quick check for the updated reset/rollback and period semantics.
78
+
79
+ ### 🙏 Thank You
80
+
81
+ Thank you for trying!
82
+
83
+ ---
84
+
4
85
  ## v0.27.2 (March 16, 2026)
5
86
 
6
87
  **Title:** Snapshot events and safer services
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@blinklabs/dingo",
3
- "version": "0.27.3",
3
+ "version": "0.27.5",
4
4
  "description": "Dingo is a Cardano blockchain data node",
5
5
  "main": "index.js",
6
6
  "bin": {