Skip to content

Update lnd documentation #349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
github-actions merged 1 commit into from
Aug 21, 2026
Merged

Update lnd documentation #349

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/lnd/release-notes/release-notes-0.20.4.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,12 @@
incoming HTLC resolver could treat a foreign commitment spend as its own
success transaction and offer a phantom input to the sweeper.

* Native SQL invoice migration [now correctly associates legacy AMP invoice
HTLCs](https://github.com/lightningnetwork/lnd/pull/11106) with their AMP
sub-invoices. Previously, the HTLC rows were inserted without those
associations, causing verification to fail and the migration transaction to
roll back.

# New Features

## Functional Enhancements
Expand Down
6 changes: 6 additions & 0 deletions docs/lnd/release-notes/release-notes-0.21.3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,12 @@
incoming HTLC resolver could treat a foreign commitment spend as its own
success transaction and offer a phantom input to the sweeper.

* Native SQL invoice migration [now correctly associates legacy AMP invoice
HTLCs](https://github.com/lightningnetwork/lnd/pull/11106) with their AMP
sub-invoices. Previously, the HTLC rows were inserted without those
associations, causing verification to fail and the migration transaction to
roll back.

# New Features

## Functional Enhancements
Expand Down