Amber nodes are monitored by CommitWatch. Gray nodes are sampled from authenticated GitHub public commit search and may not represent complete contribution history.
This commit updates a GitHub Actions workflow that runs an optional code-review bot called 'gateway'. It only changes two pinned version numbers (SHA hashes) for the bot's action and its runtime, moving from v0.5.0 to v0.6.0. There is no c…
This commit updates a GitHub Actions workflow for an optional code-review bot called 'gateway' from version 0.4.4 to 0.5.0. It adds support for replying to inline review comments (not just regular PR comments) and pins the new action and r…
Workflow-only change with no modifications to LND application codeAction and runtime pinned to immutable commit SHAs (supply-chain mitigation)New pull_request_review_comment trigger added; commit message asserts same fork-PR secret safety as issue_comment
This commit updates a GitHub Actions workflow that runs an automated code-review bot called 'gateway'. It bumps the bot's version from v0.4.3 to v0.4.4 and removes a hardcoded numeric 'installation_id'. The new version figures out the corr…
Hardcoded installation_id removed, reducing risk of using a wrong-organization GitHub App installationAction and runtime pinned to immutable commit SHAs (supply-chain best practice maintained)No changes to LND runtime, wallet, channel, or network code
This commit adds a new optional GitHub Actions workflow that lets maintainers trigger an automated code-review bot by typing '/gateway review' on a pull request. It is purely an infrastructure/configuration change and does not alter any LN…
New CI/CD workflow that consumes repository secretsWorkflow triggered by untrusted PR comments but gated to PR comments only and maintainer-gated inside the private runtimeAction and private runtime are SHA-pinned rather than tag-pinned, reducing supply-chain tag-moving risk
This commit only updates a documentation file (docs/db_migration_guide.md). It refreshes the roadmap table, a flowchart, and guidance text to reflect that the payments relational backend is now available in v0.21 and that btcwallet/channel…
This commit only adds documentation: a set of release-candidate testing guides for the upcoming LND v0.21.0 release. No source code, configuration defaults, RPC behavior, or database logic is changed. The new Markdown files describe how te…
No code changes — documentation onlyGuides mention high-risk upgrade behaviors (e.g., sqlite/postgres closed-channel tombstone downgrade trap, payment KV→SQL migration irreversibility, MinCLTVDelta breaking change), but these are descriptions of existing v0.21.0 behavior, not new changes introduced by this commitOne guide contains a TBD callout about SkipNativeSQLMigration rescue-path behavior, explicitly flagged as pending developer confirmation
This commit only updates the project's written guidelines for new contributors. It adds a section explaining that first-time contributors are encouraged to start by reviewing issues and other people's pull requests rather than submitting n…
This commit only adds a release note describing a previous documentation fix. It adds missing labels in API definitions so generated docs correctly link to command-line tool commands. There is no code change and no security issue.
This commit only updates documentation comments in protocol-buffer definitions and the generated API documentation files. It adds labels that tell readers which lncli command corresponds to three existing RPCs. No code behavior, permission…
This commit only removes two entries from the draft release notes for version 0.21.0. The entries describe bug fixes that were already merged into the earlier 0.20.1 release, so they are being deleted from the wrong document. No code was c…
This commit only adds text to the release notes document for version 0.20.1. It describes several previously merged bug fixes (TLS file handling, database race conditions, SQL connection limits, feature-bit parsing, and a gossiper deadlock…
This commit only updates the release notes document. It describes a new optional flag for the GetDebugInfo RPC and related lncli commands that controls whether log files are included in responses. There is no code change, no vulnerability,…
This commit adds a new optional --include_log flag to two LND command-line tools (getdebuginfo and encryptdebugpackage). When the user explicitly sets this flag, log file content is included in the debug output or encrypted support package…
This change makes the GetDebugInfo RPC call read the log file only when explicitly requested via a new include_log flag. Previously, every call to GetDebugInfo would read the entire log file, which could be slow or consume memory if the lo…
Performance/resource-consumption hardening: avoids reading large files by defaultRPC behavior change gated by a new request flagNo authentication or authorization changes visible in the diff
This commit adds a new optional flag called include_log to the GetDebugInfo API request in LND. When set to true, the server will return the contents of its log file along with the existing configuration map. The change is purely a protobu…
New optional API flag that can cause the server to return log file contentsLog files may contain operational or sensitive node informationDefault behavior is unchanged; explicit opt-in required
This commit simply replaces an expired PGP public key for a person named Suheb in the project's key directory. It is a routine key rotation with no code changes and no apparent security vulnerability.
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 …
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.