LND

This commit is a straightforward internal code cleanup in LND's channel graph database. It swaps one Go data type for another equivalent one (route.Vertex, which is defined as exactly the same 33-byte array) when storing public keys in channel records. There is no functional change, no bug fix, and no security-relevant behavior change.

This commit is a straightforward internal refactoring in LND's channel graph code. It introduces a new VersionedGraph wrapper so that future support for multiple gossip protocol versions can be added cleanly. For now every call site is hard-coded to use the existing V1 gossip version, so observable behavior is unchanged. There is no security fix or vulnerability here.

This commit only changes test code. It updates helper functions in the graph database test file so they can create either version 1 or version 2 Lightning Network gossip nodes, and updates existing tests to explicitly request version 1 nodes. There is no change to production code, no bug fix, and no security-relevant behavior.

This commit only adds a single line to the release notes document, describing a past code change (preparing the graph database for a future gossip protocol version). It contains no actual code changes, no bug fixes, and no security-related content.

This commit removes an unused internal cache field that stored a parsed cryptographic signature alongside the raw signature bytes. It is a straightforward code cleanup with no security-relevant behavior change: callers still access the raw signature bytes, and the only consumer is updated to set the field directly instead of through a helper method.

This commit only adds and reorganizes test code. It introduces a new test helper that runs existing node database tests against both v1 and v2 gossip data formats, and refactors one existing test to use that helper. There is no change to production code, runtime behavior, or security-sensitive logic.

This commit updates LND's internal graph database code so it can recognize and store a new type of Lightning node announcement (called 'v2 nodes'). It does not add any user-facing feature or change network behavior yet; it is plumbing work to support a future protocol version. There is no obvious security bug in the change itself.

This commit is a routine database schema update for an upcoming Lightning Network feature called "gossip v2." It adds new empty columns to tables that store node, channel, and routing-policy data, and updates the code that reads those tables to expect the new columns. It also removes an automated test that checked whether schema migrations could be safely run over and over, because the new migration uses SQL "ALTER TABLE" commands that are not naturally repeatable. There is no direct security vulnerability visible in the diff, but removing the idempotency test slightly weakens the project's safety net against migration mistakes.

This commit is a straightforward internal code refactor in LND's channel graph database. It moves the choice of which gossip protocol version to use from deep inside the database layer up to the caller layer, but still hardcodes version 1 everywhere. There is no security fix or vulnerability here; it is preparation for possible future configurability.

This commit adds a new database query helper called NodeExists. It simply checks whether a node with a given public key and version already exists in the database. There is no change to user-facing behavior, no bug fix, and no security-related content visible in the diff.

This commit is a routine internal code cleanup in the Lightning Network Daemon (LND) graph database. It splits one method, HasNode, into two methods: a simple existence check (HasNode) and a version-specific check that also returns a timestamp (HasV1Node). There is no security fix or vulnerability here.

This commit updates the database query that stores Lightning Network node announcements so it can also record a new 'block height' field used by a newer protocol version. It is a schema/query evolution, not a fix for an active security flaw. There is no indication it addresses a vulnerability.

This commit is a straightforward internal code restructure in LND's channel graph component. It stops automatically forwarding every unimplemented method to an embedded database store and instead explicitly writes out forwarding methods. The change is described by the developers as preparation for future versioning work and does not alter what the code does today. There is no security fix or vulnerability here.

This commit is a simple, mechanical rename of the graph database interface from V1Store to Store across the codebase. It changes no behavior, logic, or data handling. There is no security relevance.

This commit adds a new helper function and data structure for creating version 2 node announcements in the Lightning Network graph database. It is a straightforward feature addition with no visible security bug or fix.

This commit only fixes a code comment by removing an incomplete sentence fragment. No code logic, behavior, or security properties were changed.

This change only adjusts internal test code to fix timing-related flakiness in two watchtower client tests. It does not modify production code, so it has no direct security impact on running LND nodes.

This commit only changes a test file, increasing a timeout from 10 seconds to 60 seconds during automated tests. It is not a security fix and does not affect the production LND software that users run.

This commit is a simple code cleanup: it moves two default SQLite settings (maximum connections and busy timeout) into one shared location and removes duplicate copies elsewhere. The actual values stay exactly the same, so there is no security or functional change for users.

This commit fixes a configuration bug where LND's SQLite database layers used an unsuitable number of maximum database connections. One layer used the Postgres default (25), and another used 0 (unlimited). The patch introduces a shared SQLite-specific default of 2 connections, which matches SQLite's single-writer design and reduces resource contention. This is a reliability/resource-tuning fix rather than a direct security vulnerability, though excessive connections could contribute to denial-of-service conditions under load.

This commit fixes a minor configuration bug in LND's SQLite database support. The software had a user-configurable 'busy timeout' setting, but it was being ignored and always set to 5000 milliseconds (5 seconds). The change makes the setting actually work, falling back to 5000 ms when not configured. This is a correctness/availability improvement, not a direct security vulnerability fix.

This commit fixes a configuration bug in LND's new SQLite-based database layer. A setting called PragmaOptions existed in the config but was being silently ignored when building the database connection string. The change now appends those user-specified SQLite pragma options, matching how the older key-value SQLite store already behaves. Pragmas control low-level database behavior such as locking modes, journal settings, and synchronous levels, so honoring the user's choices matters for both correctness and security hardening.

This commit adds a new GitHub automation that uses an AI assistant (Claude Code) to detect and comment on duplicate GitHub issues. It does not change any wallet, networking, or cryptographic code in the Lightning node itself. There is no direct security risk visible in the diff.

This commit simply updates the stated minimum Go programming language version from 1.24.11 to 1.25.5 across project files and installation instructions. It does not change any application code, fix a bug, or address a security vulnerability. The build system was already using Go 1.25.5, so this is just a paperwork alignment.

This commit only changes the internal GitHub workflow that automatically labels pull requests by severity. It adjusts the bot so that command-line client files under cmd/* are classified as MEDIUM instead of HIGH, because filenames like cmd_walletunlocker.go were being incorrectly matched to security-sensitive server-side package names. There is no change to LND's actual code, no user-facing behavior change, and no security fix or vulnerability patch.