From 99f48d176974cf064a292fa6dae7ae18712dda4c Mon Sep 17 00:00:00 2001 From: Kgothatso Ngako Date: Sat, 3 Oct 2026 08:24:11 +0200 Subject: [PATCH] fix(build): restore the lightning-kmp-app pin a merge regressed `claude/focused-brattain-433b3b` was bootstrapped with the submodule at `84cc44c8` and never moved it, so every `git add -A` in that worktree staged the older gitlink over whatever `mantra` had reached. The fast-forward just carried that back here, undoing three commits of the library: the merged threshold fix, secp256k1-kmp's linux cinterop sync fix, and the advance that went with them. `e0d2b823` is what `mantra` pinned at 2f542408 and what this checkout has had checked out all along -- which is why the submodule showed as modified the moment the fast-forward landed, and is the only reason this was noticed at all. A worktree whose submodule is behind will do this again on its next `git add -A`. See docs: after a merge that moves the pin, move the submodule too. --- lightning-kmp-app | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lightning-kmp-app b/lightning-kmp-app index 84cc44c8..e0d2b823 160000 --- a/lightning-kmp-app +++ b/lightning-kmp-app @@ -1 +1 @@ -Subproject commit 84cc44c855e3d173e26016b807c449153a3af597 +Subproject commit e0d2b823dad95d56816da56116575e7564938d90