fix(build): restore the lightning-kmp-app pin a merge regressed

Browse Source

`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.

...

This commit is contained in:

Kgothatso Ngako

2026-10-03 08:24:11 +02:00

parent c0db6908a1

commit 99f48d1769

1 changed files with 1 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2

lightning-kmp-app

Submodule lightning-kmp-app updated: 84cc44c855...e0d2b823da