From b87f1f06123ed8c5ed5c6adead18ee90d1ccbb18 Mon Sep 17 00:00:00 2001 From: archipelago Date: Tue, 1 Sep 2026 18:58:33 -0400 Subject: [PATCH] chore: prepare release v1.8.10-alpha --- core/Cargo.lock | 2 +- core/archipelago/Cargo.toml | 2 +- neode-ui/package-lock.json | 4 +-- neode-ui/package.json | 2 +- releases/pending/v1.8.10-alpha/manifest.json | 29 ++++++++++++++++++++ 5 files changed, 34 insertions(+), 5 deletions(-) create mode 100644 releases/pending/v1.8.10-alpha/manifest.json diff --git a/core/Cargo.lock b/core/Cargo.lock index bdf77fbc..269f3c18 100644 --- a/core/Cargo.lock +++ b/core/Cargo.lock @@ -104,7 +104,7 @@ dependencies = [ [[package]] name = "archipelago" -version = "1.8.9-alpha" +version = "1.8.10-alpha" dependencies = [ "anyhow", "archipelago-container", diff --git a/core/archipelago/Cargo.toml b/core/archipelago/Cargo.toml index c135cdae..b07f2be7 100644 --- a/core/archipelago/Cargo.toml +++ b/core/archipelago/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "archipelago" -version = "1.8.9-alpha" +version = "1.8.10-alpha" edition = "2021" license.workspace = true description = "Archipelago Bitcoin Node OS - Native backend" diff --git a/neode-ui/package-lock.json b/neode-ui/package-lock.json index 0fc1856f..0e9fcb86 100644 --- a/neode-ui/package-lock.json +++ b/neode-ui/package-lock.json @@ -1,12 +1,12 @@ { "name": "neode-ui", - "version": "1.8.9-alpha", + "version": "1.8.10-alpha", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "neode-ui", - "version": "1.8.9-alpha", + "version": "1.8.10-alpha", "dependencies": { "@scure/bip39": "^2.2.0", "@types/dompurify": "^3.0.5", diff --git a/neode-ui/package.json b/neode-ui/package.json index efc25e79..f1ab5707 100644 --- a/neode-ui/package.json +++ b/neode-ui/package.json @@ -1,7 +1,7 @@ { "name": "neode-ui", "private": true, - "version": "1.8.9-alpha", + "version": "1.8.10-alpha", "type": "module", "scripts": { "start": "./start-dev.sh", diff --git a/releases/pending/v1.8.10-alpha/manifest.json b/releases/pending/v1.8.10-alpha/manifest.json new file mode 100644 index 00000000..9bd74fa7 --- /dev/null +++ b/releases/pending/v1.8.10-alpha/manifest.json @@ -0,0 +1,29 @@ +{ + "changelog": [ + "**Lightning sends work again — v1.8.9's payment switch lost the fee budget.** Moving payments to LND 0.21's supported route (Router.SendPaymentV2) shipped without a fee limit, and the v2 API treats an absent limit as **zero allowed fees**: every real route carries a routing fee, so the pathfinder rejected them all and the wallet answered \"No route to the recipient\" on every send — all day, on healthy channels with plenty of liquidity. The router debug log made it unambiguous (`fee_limit=0 mSAT` on every failing wallet payment; the same payment succeeded by hand the moment a fee limit was set). Payments now carry lncli's default budget (the payment amount), the wallet's amount handling for zero-value invoices is preserved, and a unit test pins the limit can never be zero again.", + "**A channel that drops its peer link now heals itself — on every node.** Restarting LND (an app update, a reboot, container churn) can leave a channel's peer connection down for hours while both endpoints keep the channel flagged disabled in the routing graph: the node looks perfectly healthy, the wallet shows balance, and every payment in either direction fails \"no route to the recipient\". Observed live: a node's only channel sat unroutable for ~17 hours after the LND 0.21.2 update, with no sign of it in any dashboard. The daemon now watches the channel graph as desired state — every open channel should have a live peer — and reconnects any that don't, using the peer's advertised addresses. Nodes without LND are untouched; an unreachable peer is retried gently, not hammered.", + "**The Lightning wallet states the node's real funding state instead of \"you have no channel.\"** Trying to send while a freshly opened channel was still waiting for on-chain confirmations — or when all its balance sits on the far side — raised a modal that claimed the node had NO channel at all (the outbound sum is legitimately zero in both states), pointed the user at opening a second channel, and — for payment routing failures — even showed the *receiving* copy. The funding gate now reads the channel list it already fetched: a confirming channel gets \"it unlocks automatically once confirmed, nothing is needed from you\", a far-side balance gets \"you can receive, but there's nothing to send right now\", a routing/liquidity payment failure says so instead of claiming channel problems, and only a genuinely channel-less node keeps the open-one guidance." + ], + "components": [ + { + "current_version": "1.8.10-alpha", + "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.10-alpha/archipelago", + "name": "archipelago", + "new_version": "1.8.10-alpha", + "sha256": "6c8bd41fed44cd999cb360c00e1b66a2d19d19812cc2b0c8a1677eec2a9579e6", + "size_bytes": 64178056 + }, + { + "current_version": "1.8.10-alpha", + "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.10-alpha/archipelago-frontend-1.8.10-alpha.tar.gz", + "name": "archipelago-frontend-1.8.10-alpha.tar.gz", + "new_version": "1.8.10-alpha", + "sha256": "6b25de8a8e1a4f7fe51594f9bbbe21f5820f417af47a8b309c2dbf8f8723b719", + "size_bytes": 97736297 + } + ], + "release_date": "2026-09-01", + "signature": "b69926bcb1851ff7d6a5b24519cd4a8015aab4ed4b588ee989d8ce6e3beaeb2cc0eb38078f522ded0d389fe53b7dbcdbf3f40c534b4bfafa5cf4a2ab2c59e40f", + "signed_by": "did:key:z6Mkfu5LT8d4DjETtrkATvHh9Dvcbnr7zBCUwfau8Sw7DLWT", + "version": "1.8.10-alpha" +}