From b050e92fe9e074446379c45ad4e7385b00ef569a Mon Sep 17 00:00:00 2001 From: humble-little-bear Date: Fri, 31 Jul 2026 07:43:41 +0000 Subject: [PATCH] chore: version packages for 0.4.11 release Consume all pending changesets and bump @offckb/cli from 0.4.10 to 0.4.11. The offckb logs changeset is downgraded from minor to patch so the release stays on the 0.4.x patch line. --- .changeset/ckb-tui-frozen-version-migration.md | 5 ----- .changeset/ckb-tui-v0.1.4.md | 5 ----- .changeset/legacy-data-upgrade-test.md | 4 ---- .changeset/logs-command-quiet-node.md | 5 ----- .changeset/tame-bears-bump.md | 5 ----- .changeset/terminal-rpc-version-compat.md | 5 ----- CHANGELOG.md | 10 ++++++++++ package.json | 2 +- 8 files changed, 11 insertions(+), 30 deletions(-) delete mode 100644 .changeset/ckb-tui-frozen-version-migration.md delete mode 100644 .changeset/ckb-tui-v0.1.4.md delete mode 100644 .changeset/legacy-data-upgrade-test.md delete mode 100644 .changeset/logs-command-quiet-node.md delete mode 100644 .changeset/tame-bears-bump.md delete mode 100644 .changeset/terminal-rpc-version-compat.md diff --git a/.changeset/ckb-tui-frozen-version-migration.md b/.changeset/ckb-tui-frozen-version-migration.md deleted file mode 100644 index fc70cf3..0000000 --- a/.changeset/ckb-tui-frozen-version-migration.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@offckb/cli': patch ---- - -Fix upgraded installs staying on an old bundled ckb-tui. Releases up to 0.4.10 wrote the entire merged settings object on any `offckb config set` (proxy or ckb-version), freezing the then-current bundled ckb-tui version (v0.1.3) into `settings.json`. After upgrading offckb, that frozen value overrode the new shipped default, so affected users never moved to v0.1.4 — and the stale-binary digest check compares against the configured version, so it never triggered a reinstall for them either. `readSettings` now upgrades a persisted ckb-tui version that is older than the shipped default (a newer hand-set version is still respected), and `writeSettings` no longer persists the version when it merely equals the default. diff --git a/.changeset/ckb-tui-v0.1.4.md b/.changeset/ckb-tui-v0.1.4.md deleted file mode 100644 index 41a1733..0000000 --- a/.changeset/ckb-tui-v0.1.4.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@offckb/cli': patch ---- - -Bump the bundled ckb-tui from v0.1.3 to v0.1.4 for `offckb status`. The new release fixes a divide-by-zero panic in ckb-tui's data-sync thread when the connected node has no peers (Officeyutong/ckb-tui#13) — the normal state of a single-node devnet — which permanently froze the Overview, Mempool, Peers, and Blockchain panels within seconds of opening the TUI. SHA-256 digests for the v0.1.4 release assets are pinned in offckb, so the download stays verifiable. diff --git a/.changeset/legacy-data-upgrade-test.md b/.changeset/legacy-data-upgrade-test.md deleted file mode 100644 index 441d282..0000000 --- a/.changeset/legacy-data-upgrade-test.md +++ /dev/null @@ -1,4 +0,0 @@ ---- ---- - -Add a legacy-data upgrade-path integration test (`scripts/legacy-data-test.sh`) and run it in CI on Ubuntu: data created by an old offckb release (0.3.4, CKB 0.113.1) must keep working with the current build — the chain continues from the old tip with the genesis hash unchanged, the legacy ckb.toml is migrated (Terminal RPC module + tcp_listen_address), the bundled chain spec is left untouched, and a fresh transfer is committed. CI and test infrastructure only; no runtime changes. diff --git a/.changeset/logs-command-quiet-node.md b/.changeset/logs-command-quiet-node.md deleted file mode 100644 index d50caf5..0000000 --- a/.changeset/logs-command-quiet-node.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@offckb/cli': minor ---- - -Unify devnet logging around the node's log files and add `offckb logs`. A foreground `offckb node` no longer relays the raw node/miner stdout: the console now shows lifecycle events, live contract script debug output (`debug!` in scripts, streamed over the node's TCP log subscription), submitted transaction hashes, and RPC errors — the full node log stays in `data/logs/run.log` as always, and `--verbose` restores the old firehose. The new `offckb logs [node|script|miner|rpc] [-f] [--grep] [--tail]` command reads those log files (`docker logs` style), so logs are reachable in every run mode — foreground, daemon, or while `offckb status` is attached — and pipe/agent friendly. The RPC proxy is quieter too: per-request lines moved from info to debug, JSON-RPC errors in responses now surface as warnings, and everything the proxy sees is appended to `data/logs/proxy.log` (viewable via `offckb logs rpc`). diff --git a/.changeset/tame-bears-bump.md b/.changeset/tame-bears-bump.md deleted file mode 100644 index 2cc37bc..0000000 --- a/.changeset/tame-bears-bump.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@offckb/cli': patch ---- - -Bump default CKB version to 0.208.0 diff --git a/.changeset/terminal-rpc-version-compat.md b/.changeset/terminal-rpc-version-compat.md deleted file mode 100644 index 09fd43d..0000000 --- a/.changeset/terminal-rpc-version-compat.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -'@offckb/cli': patch ---- - -Fix devnet startup crashing for CKB binaries older than v0.205.0. The devnet ckb.toml template enables the `Terminal` RPC module, which only exists since CKB v0.205.0; older binaries abort at startup with an opaque serde "unknown variant" error, and the legacy-config migration re-added the module on every `offckb node` start even after users removed it by hand. offckb now adapts the devnet config to the CKB version: fresh chains for an old binary are initialized without `Terminal` (the migration also stops re-adding it, while still enabling `tcp_listen_address`), a config that already has `Terminal` paired with an old binary fails fast with an actionable error instead of the serde dump, and an unprobeable custom `--binary-path` that crashes with the tell-tale "unknown variant `Terminal`" message now gets a hint pointing at the cause. The `offckb status` system-metric panels require CKB >= 0.205.0; the README's `status` section says so. diff --git a/CHANGELOG.md b/CHANGELOG.md index 668640a..07361a5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,15 @@ # @offckb/cli +## 0.4.11 + +### Patch Changes + +- e232028: Fix upgraded installs staying on an old bundled ckb-tui. Releases up to 0.4.10 wrote the entire merged settings object on any `offckb config set` (proxy or ckb-version), freezing the then-current bundled ckb-tui version (v0.1.3) into `settings.json`. After upgrading offckb, that frozen value overrode the new shipped default, so affected users never moved to v0.1.4 — and the stale-binary digest check compares against the configured version, so it never triggered a reinstall for them either. `readSettings` now upgrades a persisted ckb-tui version that is older than the shipped default (a newer hand-set version is still respected), and `writeSettings` no longer persists the version when it merely equals the default. +- 40e2317: Bump the bundled ckb-tui from v0.1.3 to v0.1.4 for `offckb status`. The new release fixes a divide-by-zero panic in ckb-tui's data-sync thread when the connected node has no peers (Officeyutong/ckb-tui#13) — the normal state of a single-node devnet — which permanently froze the Overview, Mempool, Peers, and Blockchain panels within seconds of opening the TUI. SHA-256 digests for the v0.1.4 release assets are pinned in offckb, so the download stays verifiable. +- 178379f: Unify devnet logging around the node's log files and add `offckb logs`. A foreground `offckb node` no longer relays the raw node/miner stdout: the console now shows lifecycle events, live contract script debug output (`debug!` in scripts, streamed over the node's TCP log subscription), submitted transaction hashes, and RPC errors — the full node log stays in `data/logs/run.log` as always, and `--verbose` restores the old firehose. The new `offckb logs [node|script|miner|rpc] [-f] [--grep] [--tail]` command reads those log files (`docker logs` style), so logs are reachable in every run mode — foreground, daemon, or while `offckb status` is attached — and pipe/agent friendly. The RPC proxy is quieter too: per-request lines moved from info to debug, JSON-RPC errors in responses now surface as warnings, and everything the proxy sees is appended to `data/logs/proxy.log` (viewable via `offckb logs rpc`). +- 966926b: Bump default CKB version to 0.208.0 +- 01fd059: Fix devnet startup crashing for CKB binaries older than v0.205.0. The devnet ckb.toml template enables the `Terminal` RPC module, which only exists since CKB v0.205.0; older binaries abort at startup with an opaque serde "unknown variant" error, and the legacy-config migration re-added the module on every `offckb node` start even after users removed it by hand. offckb now adapts the devnet config to the CKB version: fresh chains for an old binary are initialized without `Terminal` (the migration also stops re-adding it, while still enabling `tcp_listen_address`), a config that already has `Terminal` paired with an old binary fails fast with an actionable error instead of the serde dump, and an unprobeable custom `--binary-path` that crashes with the tell-tale "unknown variant `Terminal`" message now gets a hint pointing at the cause. The `offckb status` system-metric panels require CKB >= 0.205.0; the README's `status` section says so. + ## 0.4.10 ### Patch Changes diff --git a/package.json b/package.json index 29259b2..040a729 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@offckb/cli", - "version": "0.4.10", + "version": "0.4.11", "description": "ckb development network for your first try", "author": "CKB EcoFund", "license": "MIT",