LND

This commit fixes a bug in LND's gossip syncer where a background goroutine could get stuck in an endless loop when a peer disconnected or its work was cancelled. Instead of exiting cleanly, the goroutine would repeatedly try the same step, flood error logs, and never stop. The fix makes the goroutine return errors to its main loop so it can shut down properly.

This change makes LND more forgiving when reading old payment failure records that contain slightly corrupted extra data fields. Previously, such records could cause the database read to fail entirely; now the code logs a warning and continues, leaving the failure message empty but preserving the rest of the record. It is a robustness fix rather than an active vulnerability patch.

This commit only changes a single version string from 'beta.rc2' to 'beta.rc3' in the software's build metadata. It is a routine release-candidate version bump with no functional code changes and no security relevance.

This commit only adds a new documentation file explaining how LND node operators can migrate their database from the legacy bbolt format to SQLite or PostgreSQL. It contains no code changes, no configuration changes, and no security fixes or vulnerabilities.

This commit only updates the release notes document for version 0.20.0. It adds a description of a previously fixed bug about wallet rescanning during header sync. No code changes are included, so this commit itself does not alter software behavior or introduce security risk.

This patch fixes a startup-order bug in the Lightning Network Daemon (LND). Because a previous change started the chain notifier before the wallet's block headers were fully synced, rescans could begin from an old block height roughly 100,000 blocks behind the current chain tip. The fix moves chain notifier startup to after header synchronization and delays the 'starting beat' block reference until after the notifier is running. The main risk is operational/money-loss: a node that rescans from a stale height can miss recent on-chain events such as channel closes, force-closes, or swept funds, which may lead to incorrect balances or delayed detection of transactions. It is not a remote code execution or direct theft vulnerability.

This commit fixes a single-character typo in the user documentation. The command example showed '-multi_file' instead of the correct '--multi_file'. It does not change any code, commands, or security behavior.

This commit simply refreshes an expired PGP public key file used to verify software releases. The same cryptographic key is kept, but its expiration date is extended. There is no code change and no security vulnerability.

This commit fixes a broken hyperlink in a documentation file. The old URL was missing a slash between 'master' and 'docs', making it invalid. The fix replaces it with a proper relative link. There is no code change and no security impact.

This commit updates a dependency called go-viper/mapstructure from version 2.3.0 to 2.4.0 across several parts of the LND project. The commit message says the older version could leak sensitive information into logs when handling malformed data, and this update fixes that. The actual code change is only to version numbers in Go module files; no LND source code is changed. We can see the stated security reason but have no independent details about exactly what data could leak or how severe the upstream bug was.

This commit is a routine build-maintenance change. It updates the version of the Go programming language used by the project's automated tests, release builds, Docker images, and documentation from Go 1.25.2 to Go 1.25.3 (and the minimum required Go version from 1.24.8 to 1.24.9). There are no code logic changes, no bug fixes, and no security patches in the project itself.

This commit changes the release build pipeline to use a more thorough disk cleanup step before compiling. It is purely a reliability improvement for GitHub Actions builds and has no security relevance.

This commit only changes a GitHub Actions workflow that deletes unused software from build machines to free up disk space. It is a routine infrastructure/maintenance change and does not modify any wallet, network, or cryptographic code. There is no security issue visible in the diff.

This commit changes the release build script to clear Go's temporary build cache after compiling for each platform. It is a routine build-hygiene fix to prevent disk space from running out during long release builds. There is no security vulnerability here.

This commit only changes a single version string from 'beta.rc1' to 'beta.rc2' in the software's build metadata. It is a routine release-candidate version bump with no functional code changes and no security relevance.

This commit only adds a line to the release notes describing a prior bug fix: HTLCs (payment contracts) with a locktime of 0 were not being swept by an older legacy sweeper component called utxonursery. The actual code fix is in a separate pull request referenced by the note. Because this commit is documentation-only, it does not itself change any program behavior, but it confirms a past bug existed that could have left some funds unrecovered.

This commit fixes a bug in LND's UtxoNursery where old HTLC outputs stored with a 0-block locktime could not be properly rescanned because the chain notifier rejects height hints of 0. The patch adds a fallback that derives a valid height hint from the channel's close height or short channel ID. It is a defensive fix for a historical data corruption issue, not a remote-exploitable vulnerability.

This commit is a routine build-maintenance change. It updates the Go compiler version used in CI, release pipelines, Docker images, and documentation from Go 1.24.6 to Go 1.25.2, and bumps the minimum Go version declared in go.mod files from 1.24.6 to 1.24.8. There are no code logic changes and no security fix or vulnerability patch is visible in the diff.

This commit is a routine dependency housekeeping change. It removes two temporary local overrides in the Go module file and switches to published versions of internal helper packages (fn v2.0.9 and sqldb v1.0.11). There is no indication in the commit or supplied references that this fixes a security issue.

This commit fixes a bug in LND's channel graph database where applying the exact same Lightning channel policy update twice in one batch would cause an error. The fix makes the code ignore the harmless duplicate instead of failing. It is a robustness improvement rather than a clear-cut security vulnerability, but the prior failure path could have caused database errors or inconsistent graph state during normal network operation.

This change fixes a database error that could occur when the same Lightning Network node announcement was processed twice in quick succession. Instead of crashing or returning an error, the code now ignores the duplicate. It is a robustness fix rather than a vulnerability that allows theft or remote takeover.

This commit is a one-word documentation update. It adds 'Graph' to the list of subsystems that support native SQL tables in the description of a configuration option. There is no code behavior change, no bug fix, and no security relevance.

This is a one-character logging fix. The developer changed a debug log message from using %x (which prints data as hexadecimal) to %s (which prints as a regular string). It does not change program behavior, fix a crash, or address any security issue. It is purely a cosmetic/log readability correction.

This is a one-line documentation update to the sample configuration file. It adds 'Graph' to a comment listing which LND database subsystems support native SQL tables. There is no code change, no behavior change, and no security relevance.

This change is a build-script hardening fix, not a security vulnerability. It makes the release script prefer GNU gzip over the default macOS BSD gzip so that release tarballs are byte-for-byte identical (reproducible) across different developer machines. There is no attacker-controlled behavior or user data at risk.