LND

This commit only touches test files. It adds t.Helper() declarations to test helper functions and adds two TODO comments about making tests database-agnostic. There are no changes to production code, no security fixes, and no behavior changes.

This commit only renames five test functions in a single test file to remove the 'KVPaymentsDB' prefix from their names. No production code, logic, or behavior was changed. It is a code-cleanup/refactoring change with no security relevance.

This commit only moves existing payment database tests from one test file to another and makes a small helper function skip its work for non-key-value database backends. There are no changes to the actual production code that runs a Lightning node, so it cannot introduce a security vulnerability or fix one.

This commit is purely a refactoring of test code. It moves payment database tests and helper functions between files so that tests not tied to the key-value backend can be reused with a future native database implementation. No production code is changed, and there is no security fix or vulnerability introduced.

This is a small test-only change in the LND Lightning Network Daemon project. It updates one test helper function to fetch payments using a different database query method so the test can work with multiple database backends. There is no change to production code, no user-facing behavior change, and no security fix.

This commit is a simple test-only rename. It changes the names of two internal helper functions used only in test files: `assertPaymentStatus` becomes `assertPaymentstatus`, and `assertPayments` becomes `assertDBPayments`. No production code is modified, and no behavior changes. There is no security relevance.

This commit only fixes a misleading comment for the InitPayment method. No code behavior was changed, so there is no security impact.

This commit is a straightforward internal code cleanup: it replaces a direct reference to a specific payments database implementation with a new Go interface. No behavior changes, bug fixes, or security fixes are visible in the diff. It simply lets different database backends satisfy the same interface in the future.

This commit moves a daily check of PGP key expiration from the release workflow to the daily Docker build workflow. It is a routine CI/CD housekeeping change. It does not fix a vulnerability, change cryptographic code, or alter how releases are signed. The change makes the check run more frequently and allows it to fail without blocking a release.

This commit only adds a new integration test for LND. It checks that a node's public announcement settings—like its alias, color, and network addresses—are saved correctly across restarts and that command-line config values take priority over previously updated values. There is no change to production code and no security fix.

This commit only adds a line to the release notes document describing a previously merged feature. It does not change any program code, configuration, or behavior. There is no security issue in this commit itself.

This commit changes how the LND lightning node rebuilds its public profile (alias, color, network addresses, and features) when it restarts. Previously, LND always rebuilt the profile from the current configuration file, which could unintentionally overwrite values that had been set or advertised during the previous run. Now, LND first checks what it previously advertised on disk and reuses those values when the configuration has not explicitly changed them. This is a consistency and reliability improvement, not a direct security fix, though it reduces the chance of accidental network identity changes that could confuse peers.

This commit only fixes a mismatch between error messages and actual timeout durations in test helper code. It does not change production behavior or fix any security issue.

This commit adds a new automated CI check that warns if the project's release signing PGP keys are about to expire. It does not change any application code, fix a bug, or alter how LND runs. It is purely a release-process safety improvement.

This commit adds a brand-new shell script that checks whether the project's PGP signing keys are expired or about to expire. It does not change any existing code, network behavior, or cryptographic handling. It is purely a release-engineering helper to catch key-expiry problems early.

This commit is a simple code cleanup: it moves two data structures (PaymentsQuery and PaymentsResponse) from one file to a new file and renames them to Query and Response because the 'Payments' prefix is no longer needed now that they are in their own package. No behavior changes, no bug fixes, and no security relevance.

This commit only adds plain-English comments to two existing variables in the payments database code. It does not change any program logic, data handling, or behavior, and therefore has no security relevance.

This commit is a straightforward internal code reorganization: it moves the PaymentCreationInfo data structure from the channeldb package into the payments/db package and updates all references accordingly. There is no functional change, no bug fix, and no security-relevant behavior change visible in the diff.

This commit is a straightforward internal code cleanup: it moves the FailureReason type and its constants from the channeldb package to the payments/db package, then updates all references across the codebase. There is no functional change to how payments fail or how failure reasons are reported to users. It is not a security fix and does not introduce any obvious security issue.

This commit is a routine code cleanup titled 'fix linter'. It removes blank lines, unused test variables, and outdated linter suppression comments. The only functional change is adding a type-safety check when reading payment updates from a stream, which now returns a clear error instead of potentially panicking if an unexpected type appears. There is no indication this fixes an active security vulnerability.

This commit is a large but straightforward code refactor: it moves payment-related data structures, database logic, and tests out of the `channeldb` package into a new `payments/db` package. The commit message explicitly says it is the smallest move possible to avoid import cycles and keep the change set small. No security fixes, behavior changes, or vulnerability patches are visible in the diff.

This commit only expands an existing developer helper test in the LND codebase. It adds configuration options so engineers can locally test migrating graph data between different database backends (bbolt, sqlite, postgres). The test is skipped by default and does not change any production code, network behavior, or user-facing functionality. There is no security issue here.

This commit only adds a line to the release notes document describing a previously merged database index improvement. No code changes are present, and there is no security relevance in the diff itself.

This commit adds a new documentation file explaining how SQL database schema updates should be written in LND. It contains no code changes, no configuration changes, and no fixes. It is purely a developer guide.

This commit reorganizes database migration files for the LND Lightning node software. It moves a new invoice index migration into the main production migration sequence and renumbers the graph-related migration files so they remain in chronological order. There are no code changes that fix or introduce a security vulnerability; it is purely a schema-management cleanup.