LL
← All projectsLightning Labs

LND

Go implementation of a complete Lightning Network node.

BitcoinLightning NetworkNormal
Repository coverage

1687 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

186security candidates236second-pass queue1372AI analyses
162commits · 30 days
278commits · 60 days
643commits · 180 days
1422commits · 365 days
Backfill bands
Aug 5 → Feb 6405 seen5 candidatesComplete
Feb 6 → Jun 6665 seen28 candidatesComplete
Jun 6 → Jul 689 seen4 candidatesComplete
Jul 6 → Aug 569 seen0 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
387Strong · 80–100
837Adequate · 60–79
432Thin · 40–59
31Opaque · 0–39
1security candidate with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Olaoluwa Osuntokun29659235474
ziggie49922422265
Elle Mouton26832268167
Yong60926172
ziggieXXX50617170
George Tsagkarelis37335167
LNBiG111173
Jared Tobin909171
yyforyongyu1211574070
bitromortac731154071
Erick Cestari26726070
Suheb746074
Analysis record

Published AI watches

Last scanned 43 minutes ago

Low 43 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11588 from ziggie1984/lnwallet/fix-reorg-wallet-sync-flake

This change fixes a wallet synchronization check in LND. Previously, the wallet only compared block heights to decide if it was fully caught up with the Bitcoin chain. During a chain reorganization (a temporary fork where one block is repl…

State synchronization check previously used height only, which is insufficient across reorgsFix adds block hash comparison to prevent false-positive sync statusCould cause LND to proceed while wallet state reflects an invalidated or not-yet-updated chain tip
8cdbf85cby Yong+224−1354 files
Vendor flagged security relevance
Moderate 51 AI analysisMessage 68 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #10708 from jtobin/alias-perms

This commit fixes a missing permission check on a new Lightning routing RPC called XFindBaseLocalChanAlias. Without the entry, any valid macaroon could call that RPC, bypassing the normal access-control list. The patch adds the required pe…

Missing macaroon authorization entry for an RPC endpointPotential privilege escalation: any valid macaroon could invoke an unprotected RPCRegression test added to enforce macPermissions coverage
98dc2b44by Olaoluwa Osuntokun+35−02 files
No security note in commit
Moderate 68 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11555 from yyforyongyu/invoice-settlement-public

This large LND patch changes when an ordinary invoice is considered 'paid'. Previously, releasing the preimage (the secret that lets the payer claim the funds) immediately marked the invoice as settled. Now the invoice enters a new interme…

New intermediate invoice/HTLC state prevents premature settlement reportingOn-chain HTLC outcomes persisted without opt-in to support restart recoveryForwarding package marker persisted before preimage release to avoid replay rejection on restart
895118acby Olaoluwa Osuntokun+4536−32048 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 80 · Strong
LL Lightning LabsLND BitcoinLightning Network

docs: describe invoice collection finality

This commit only adds documentation to the release notes. It describes a previously merged code change (PR 11555) about how LND handles invoice finality, but the commit itself contains no code, bug fixes, or behavior changes. There is noth…

9649d9f6by yyforyongyu+87−01 file
No security note in commit
Moderate 64 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11551 from ziggie1984/public-pr149-sanitized

This change fixes a bug in LND's invoice handling for multi-part payments (MPP and AMP). When a payment is split into several pieces (HTLCs), each piece is accepted individually. Previously, an old accepted piece could become too close to …

Fixes missing revalidation of accepted HTLC CLTV expiries at MPP/AMP set completionPrevents settlement of shards whose on-chain claim window has become unsafe while heldAdds new fail resolution ResultHtlcSetExpiryTooSoon and cancels the entire affected set
4b7447bcby Yong+281−347 files
Vendor flagged security relevance
Low 35 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11396 from yyforyongyu/task-lease-policy

This commit changes how LND's wallet locks (leases) unspent coins through its RPC interface. It removes a recently added 'release after N confirmations' option and replaces it with an explicit 'no expiry' flag. Old clients that still send …

Breaking API change that reserves removed protobuf fields to prevent accidental reintroductionExplicit rejection of legacy `release_after_spend_confs` parameters from old clients instead of silent fallbackValidation prevents conflicting no-expiry + duration lease settings before wallet state is touched
03e28a96by Yong+663−4029 files
Vendor flagged security relevance
Low 40 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11175 from ViktorT-11/2026-08-gossip-version-agnostic-store

This commit refactors how the Lightning Network Daemon (LND) stores and queries channel graph data so that the same channel or node can exist under both old (v1) and new (v2) gossip protocols without the database returning stale, missing, …

Cross-version data consistency: prevents a v2 channel shell from shadowing a usable v1 channel, which could affect routing decisions and RPC output.Cache consistency: ensures the in-memory pathfinding cache and the SQL-backed RPC reads agree on which channel version and policies are active.Bug fix: zombie edge info now carries the correct channel ID instead of 0, which could have caused incorrect channel identification during resurrection.
8c251687by Yong+3752−28726 files
No security note in commit
Moderate 61 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11440 from Roasbeef/fix-longstanding-correctness-bugs

This is a large bug-fix patch for LND (a Bitcoin Lightning Network node) that tightens correctness rules across many subsystems. It prevents several ways a node could mis-handle channel data, accept bad network gossip, commit corrupted dat…

Database transaction commit now aborts on read errors (etcd) - prevents silent data corruption / inconsistent stateGossip zombie marking removed for invalid funding script - prevents denial-of-service / channel graph poisoningWire message length bounding added to watchtower protocol - prevents memory exhaustion / malformed message parsing
0123a548by Olaoluwa Osuntokun+1424−11938 files
Vendor flagged security relevance
Moderate 59 AI analysisMessage 80 · Strong
LL Lightning LabsLND BitcoinLightning Network

invoices: require complete payment collection

This commit changes how LND handles multi-part Lightning payments when one part fails after the preimage was already released. Previously, the invoice could be marked as fully paid even if one shard was later reclaimed by the payer on-chai…

Changes invoice settlement semantics for released-but-failed HTLCsAdds new persisted HTLC state `HtlcStateFailed`Prevents invoice from reaching `ContractSettled` when any released shard fails
699ea930by Olaoluwa Osuntokun+492−4910 files
No security note in commit
Moderate 60 AI analysisMessage 78 · Adequate
LL Lightning LabsLND BitcoinLightning Network

lnwallet: reject a zero CSV delay

This change tightens the rules for opening Lightning payment channels by refusing a setting called the CSV delay when it is set to zero. The CSV delay is the waiting period a user must endure before reclaiming their own funds from a channe…

Rejects a zero CSV delay that would eliminate the breach-remedy windowCentralizes the check in VerifyConstraints so all channel types and directions are coveredAdds explicit error type and unit test for the new constraint
266eba7bby Olaoluwa Osuntokun+81−03 files
Vendor flagged security relevance
Moderate 58 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

lnwallet+chanstate: keep persisted HTLC data readable

This commit fixes two bugs in how Lightning Network channel data is saved to disk. First, it stops extra 'aux' signatures meant only for advanced taproot channels from being saved on ordinary channels, where they don't belong. Second, it p…

Persisted state could become unreadable due to writer/reader size mismatchAuxiliary signatures for taproot overlay channels were persisted on plain channel HTLCsFix adds explicit serialization bound to prevent unreadable channel records
43c74723by Olaoluwa Osuntokun+101−25 files
No security note in commit
Low 39 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11374 from bitromortac/20261016-c7e5-dispatch

This commit adds the first end-to-end BOLT 12 'Offers' flow to LND: a new dev-only RPC and CLI command to create offers, plus a dispatcher that listens for incoming onion-message invoice requests and replies with signed BOLT 12 invoices. I…

New network-facing dispatcher answers invoice requests from any peer; rate and concurrency limits are appliedBlinded-path PathID check prevents reply linking to self-created paths, but TODO notes the check should move once offers can have offer_pathsCreateOffer RPC is restricted to dev builds and requires offchain:write macaroon permission
a9d4ca3bby bitromortac+3113−7838 files
No security note in commit
Moderate 60 AI analysisMessage 78 · Adequate
LL Lightning LabsLND BitcoinLightning Network

invoices: reject settled AMP set shards

This change fixes a bug in LND's invoice handling for AMP (Atomic Multi-Path) payments. Previously, if someone tried to pay a fresh shard for an AMP set that was already fully paid, the invoice updater could return an internal error that w…

Denial-of-service vector: an internal updater error could force-fail a shared channel link, disrupting unrelated sibling HTLCsAMP invoice state machine edge case: reusable invoice stays open for other sets but must reject new shards for already-settled setsClean failure path introduced: ResultInvoiceNotOpen instead of error-driven link failure
99e3da37by yyforyongyu+49−02 files
No security note in commit
Moderate 59 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11282 from lightningnetwork/elle-base-branch-payment-service

This is a large feature merge for LND that adds a new optional RPC subsystem called switchrpc. It lets an external program hand a pre-built onion packet to LND for direct dispatch over a Lightning channel, instead of LND doing its own path…

New optional RPC surface (switchrpc) that accepts externally crafted onion packets and directly dispatches HTLCsIdempotency/deduplication added via InitAttempt durable write-ahead log and ErrPaymentIDAlreadyExistsStartup orphan cleanup fails half-open or pre-commit attempts to avoid hangs
11f79be0by Olaoluwa Osuntokun+11385−22458 files
Vendor flagged security relevance
Low 44 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11472 from yyforyongyu/task-sweep-rejections

This commit fixes a bug in LND's transaction sweeping logic. Previously, if the Bitcoin backend rejected a sweep transaction for a temporary or unknown reason (for example, the mempool was full, a network error occurred, or the rejection r…

Funds-availability / liveness fix: temporary or unknown mempool rejections could leave sweep inputs unspent.Error-handling reclassification: previously fatal errors now retryable.Retry metadata preservation: next fee rate and fee cap kept across attempts.
c5863e55by Yong+290−9720 files
No security note in commit
Low 32 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11292 from ViktorT-11/2026-10-harden-remote-signing-no-op

This change is a hardening fix for LND's remote-signing feature. Previously, if a node was configured to act as an outbound remote signer but was compiled without the required 'signrpc' and 'walletrpc' sub-servers, it would silently fall b…

silent-degradation-to-no-op preventedconfiguration-misconfiguration now surfaces as fatal errorbuild-tag-dependency explicitly validated at runtime
0c538e1fby Suheb+241−125 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

invoices: fix test whitespace

This commit only fixes blank-line spacing in a single test file to satisfy lint checks. It adds one blank line after a function signature and removes one trailing blank line. There are no code behavior changes, no bug fixes, and no securit…

a67d07f4by yyforyongyu+1−11 file
No security note in commit
Low 31 AI analysisMessage 92 · Strong
LL Lightning LabsLND BitcoinLightning Network

build: pin the new lint job actions by commit

This change updates two GitHub Actions used in the project's automated lint workflow so they are locked to specific commit hashes instead of floating version tags. A floating tag could be silently repointed to a different, possibly malicio…

CI/CD supply-chain hardeningthird-party action pinning by commit hashprevention of tag-movement attacks
2a9f137dby Olaoluwa Osuntokun+4−21 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 92 · Strong
LL Lightning LabsLND BitcoinLightning Network

build: fix the custom linter cache wiring for CI

This commit fixes the GitHub Actions CI setup for running a custom code linter. It makes sure Docker can read and write build caches correctly and that the built linter image is available for later steps. There is no user-facing security f…

6f665663by Olaoluwa Osuntokun+30−82 files
No security note in commit
Moderate 66 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

Merge pull request #11482 from Roasbeef/pub/unsigned-acked-wrap

This patch fixes a database bug in the Lightning Network Daemon (LND) where very long lists of unsigned, acknowledged channel updates could be silently truncated when saved to disk. Because the storage format used a 16-bit counter, lists l…

Integer truncation / wrap-around in serialization format (uint16 count)Silent data loss on restart due to undersized length fieldDefensive deserialization with count-modulo validation
7431093fby Olaoluwa Osuntokun+218−127 files
Vendor flagged security relevance
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-priorityrpcserver: support partial channel policy updatesby saubyk · 8636a8d4 · Nov 6, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · saubyk

rpcserver: support partial channel policy updates

Move the request validation and conversion of UpdateChannelPolicy into
channelPolicyFromRequest and honor partial_update there. Non-zero values
for fields not marked in partial_update are rejected rather than
silently ignored.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritylncli: only update the policy fields that are passedby saubyk · e3c24907 · Nov 6, 2026 · 3 filesMessage 93 · StrongTriage 0Details
Commit message · saubyk

lncli: only update the policy fields that are passed

updatechanpolicy no longer requires base_fee_msat, fee_rate and
time_lock_delta on every call; fields that aren't passed keep their
current value. The flags are now string flags parsed explicitly, which
removes the misleading "(default: 0)" from the help text and rejects
invalid input instead of treating it as zero.

Individual fields are set with the flags. Positional arguments are only
accepted when all three fields are set, since it's otherwise ambiguous
which field a value fills. A trailing channel point is recognised by its
colon, so it's never read as a policy field, and any argument left over
after the policy values and one channel point is rejected.

An lnd that predates partial updates would reset an omitted fee to zero,
so lncli checks the version first and refuses such an update.

Fixes #1523.

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Lower-prioritylnrpc: add partial_update to PolicyUpdateRequestby saubyk · aa466dd3 · Nov 6, 2026 · 3 filesMessage 76 · AdequateTriage 0Details
Commit message · saubyk

lnrpc: add partial_update to PolicyUpdateRequest

PolicyUpdateRequest can't tell an unset base fee, fee rate or time lock
delta from zero, so every update has to send all three. Add an opt-in
partial_update message that marks which of the three fields to apply,
so callers can update individual fields. Without partial_update the
existing semantics are unchanged, as current clients rely on omitted
(zero) values being applied.

Fixes #1523.

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queuedMerge pull request #11472 from yyforyongyu/task-sweep-rejectionsby Yong · c5863e55 · Nov 5, 2026 · 20 filesMessage 73 · AdequateLow 44Details
Commit message · Yong

Merge pull request #11472 from yyforyongyu/task-sweep-rejections

sweep: retry transient mempool rejections

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discountsecond-pass: unusually broad change
AI analysis · Low 44/100

This commit fixes a bug in LND's transaction sweeping logic. Previously, if the Bitcoin backend rejected a sweep transaction for a temporary or unknown reason (for example, the mempool was full, a network error occurred, or the rejection reason was unclear), LND would treat the inputs as permanently failed and stop trying to spend them. The fix makes LND retry these inputs later while preserving the intended fee increase schedule, so funds are not left stuck. It also updates the required Go version to 1.27.3 across the project.

Security candidateMerge pull request #11292 from ViktorT-11/2026-10-harden-remote-signing-no-opby Suheb · 0c538e1f · Nov 5, 2026 · 5 filesMessage 73 · AdequateLow 32Details
Commit message · Suheb

Merge pull request #11292 from ViktorT-11/2026-10-harden-remote-signing-no-op

Follow-up of #8754: Harden remote signing no op

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarydefensive validationsigning or wallet pathmerge-commit duplicate discount
AI analysis · Low 32/100

This change is a hardening fix for LND's remote-signing feature. Previously, if a node was configured to act as an outbound remote signer but was compiled without the required 'signrpc' and 'walletrpc' sub-servers, it would silently fall back to a no-op client. That left the signer node running and appearing healthy while never connecting to the watch-only node, and the watch-only node would wait indefinitely for a signer that never arrives. The patch makes this a fatal startup error with a clear message naming the missing build tags and how to rebuild. It also centralizes the 'is this a signer node?' check so future graduation out of experimental mode only needs one code change.

Lower-priorityMerge pull request #11523 from yyforyongyu/task-master-lintby Yong · 77f8da4d · Nov 5, 2026 · 1 fileMessage 68 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11523 from yyforyongyu/task-master-lint

invoices: fix registry test whitespace

68/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Security candidateinvoices: fix test whitespaceby yyforyongyu · a67d07f4 · Nov 5, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · yyforyongyu

invoices: fix test whitespace

Add the required blank line after the multiline registry test helper
signature and remove the trailing blank line in the AMP replay test.
This clears the two whitespace lint failures inherited from master.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundary
AI analysis · Informational 15/100

This commit only fixes blank-line spacing in a single test file to satisfy lint checks. It adds one blank line after a function signature and removes one trailing blank line. There are no code behavior changes, no bug fixes, and no security implications.

Lower-prioritysweep: track already accepted transactionsby yyforyongyu · ec5a855a · Nov 5, 2026 · 3 filesMessage 88 · StrongTriage 0Details
Commit message · yyforyongyu

sweep: track already accepted transactions

Allow already-accepted initial transactions to reach normal publication
and tracking. A publication error can follow backend acceptance, so an
identical retry must not discard the sweep claims as fatal.

Keep the shared replacement check unchanged to avoid reporting a
byte-identical fee bump as a replacement. Cover the public outcome.

Review: https://github.com/lightningnetwork/lnd/pull/11472
Comment: 4473647569.

88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Lower-prioritysweep: bound broadcast result waitsby yyforyongyu · 9017f386 · Nov 5, 2026 · 1 fileMessage 86 · StrongTriage 0Details
Commit message · yyforyongyu

sweep: bound broadcast result waits

Bound missing result delivery in the immediate and retry tests using
the existing select timeout pattern. Broadcast remains synchronous.

Review: https://github.com/lightningnetwork/lnd/pull/11472
Comments: 4473489224, 4473491160.

86/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Lower-prioritysweep: clarify retry event semanticsby yyforyongyu · dc5bb0df · Nov 5, 2026 · 2 filesMessage 76 · AdequateTriage 0Details
Commit message · yyforyongyu

sweep: clarify retry event semantics

Describe retryable backend failures separately from terminal errors.
Qualify the earlier fee-trajectory wording: the returned rate is retry
metadata. Far-deadline capped starts retain zero-delta re-estimation.

Review: https://github.com/lightningnetwork/lnd/pull/11472
Comments: 4473396376, 4473676263.

76/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-priorityMerge pull request #11492 from ziggie1984/public-pr127-sanitizedby Yong · 25406e1a · Nov 5, 2026 · 9 filesMessage 73 · AdequateTriage 0Details
Commit message · Yong

Merge pull request #11492 from ziggie1984/public-pr127-sanitized

contractcourt: recover settled AMP HTLCs on-chain

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validationmerge-commit duplicate discount
Lower-priorityMerge pull request #11505 from lightningnetwork/ci-persist-lint-cacheby Olaoluwa Osuntokun · 7669a85c · Nov 5, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11505 from lightningnetwork/ci-persist-lint-cache

ci: persist golangci-lint analysis cache between runs

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Lower-priorityci: persist golangci-lint analysis cache between runsby Olaoluwa Osuntokun · 0d5172b7 · Nov 5, 2026 · 2 filesMessage 85 · StrongTriage 0Details
Commit message · Olaoluwa Osuntokun

ci: persist golangci-lint analysis cache between runs

In this commit, we persist golangci-lint's per-file analysis cache in
the GitHub Actions cache store so the lint job stops re-typechecking the
whole repository from scratch on every run.

The lint targets bind mount ~/.cache/golangci-lint into the tools
container, but nothing persisted that directory between runs, so each job
started with an empty analysis cache ("File cache stats: 0 entries of
total size 0B" in the logs) and re-analyzed every package.

Every run restores the most recent snapshot, keyed by the lint config,
the tools module and the custom linter plugin sources, so a run never
reuses analysis results produced by a different linter. Only the nightly
master run saves a new snapshot: entries created by PR and merge queue
runs are only readable by that same PR and by master, and the repo's
shared cache space is already at its size limit. The save runs after
both lint steps and also when they failed, so the analysis that did run
isn't lost. A cancelled run saves nothing.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
documentation-only discount
Lower-priorityMerge pull request #11504 from lightningnetwork/ci-cache-custom-linterby Olaoluwa Osuntokun · 3422068c · Nov 5, 2026 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11504 from lightningnetwork/ci-cache-custom-linter

build: cache custom linter build in CI

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
merge-commit duplicate discount
Lower-prioritybuild: export the linter cache from the nightly run onlyby Olaoluwa Osuntokun · 7d4d129d · Nov 5, 2026 · 2 filesMessage 97 · StrongTriage 0Details
Commit message · Olaoluwa Osuntokun

build: export the linter cache from the nightly run only

In this commit, we restrict the BuildKit cache export to the nightly
run and make export failures non-fatal.

The measured image export is roughly 650 MiB per run, because the GHA
backend exports the final image's layers including the Go toolchain base
layers, even with mode=min. Exporting on every PR push would therefore
fill the repo's shared cache store, which is already at its limit, and
evict the Go build caches that all jobs depend on. A PR-created cache
is only readable by that same PR and by master, so the writes mostly
help nobody. The nightly master run now writes the cache, and every
other run still reads it.

The export also gains ignore-error=true, so a cache service outage or
rate limit can't fail the lint job, and the build drops -q in favor of
--progress=plain so the logs show whether the cache was restored.

97/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Security candidatebuild: pin the new lint job actions by commitby Olaoluwa Osuntokun · 2a9f137d · Nov 5, 2026 · 1 fileMessage 92 · StrongLow 31Details
Commit message · Olaoluwa Osuntokun

build: pin the new lint job actions by commit

In this commit, we pin both actions the lint job newly uses by their
commit hash rather than by their mutable major tag, matching how the
other workflows in this repo pin third-party actions. A moved tag can
otherwise change what a lint run executes without any review.

92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
access controldocumentation-only discount
AI analysis · Low 31/100

This change updates two GitHub Actions used in the project's automated lint workflow so they are locked to specific commit hashes instead of floating version tags. A floating tag could be silently repointed to a different, possibly malicious commit, meaning the project's own build servers might run unexpected code. The patch is a preventive hardening measure, not a fix for an active attack.

Lower-prioritybuild: write the linter image cache on every CI runby Olaoluwa Osuntokun · 160d6547 · Nov 5, 2026 · 2 filesMessage 85 · StrongTriage 0Details
Commit message · Olaoluwa Osuntokun

build: write the linter image cache on every CI run

In this commit, we drop the nightly-only gate on the linter image cache
export again.

The gate was keyed on the workflow_call tier input, which only exists in
the unmerged CI tiering stack; on this branch's base there is no nightly
caller at all, so the gate would have left the cache unwritten by anyone.
The cache is also useful per pull request: an entry saved by a PR is
restored by later pushes to that same PR, which is the common iterative
case.

To bound the shared cache space we export only the layers of the final
image (mode=min) instead of every intermediate layer, which skips the
unmodified golang base image layers that live in the public registry
anyway.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-priorityMerge pull request #11501 from lightningnetwork/yy-claudell-ci-required-check-cleanupby litbot-9000 · 8d931c1a · Nov 5, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · litbot-9000

Merge pull request #11501 from lightningnetwork/yy-claudell-ci-required-check-cleanup

ci: skip matrix jobs at the job level outside their tier

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Security candidatebuild: fix the custom linter cache wiring for CIby Olaoluwa Osuntokun · 6f665663 · Nov 5, 2026 · 2 filesMessage 92 · StrongInformational 15Details
Commit message · Olaoluwa Osuntokun

build: fix the custom linter cache wiring for CI

In this commit, we fix two problems in the previous iteration of the
linter build cache.

The gha cache backend reads its credentials from the ACTIONS_RUNTIME_TOKEN
and ACTIONS_RESULTS_URL environment variables, but those are not exposed
to plain run: steps by default. We add the crazy-max/ghaction-github-runtime
step to expose them before the lint steps, otherwise the cache import or
export fails inside the manually invoked docker build.

The docker-container driver that setup-buildx-action installs doesn't
load the built image into the docker image store by default, but the lint
targets run the image with docker run. We add --load so the tagged
lnd-tools image is available to the lint steps.

We also only export the cache from the nightly run (LINT_WRITE_CACHE),
since PR-created caches aren't readable by other PRs and would only
churn the shared cache store. PR and merge queue runs still read the
cache that the nightly run exports.

92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
credential or privilege state
AI analysis · Informational 15/100

This commit fixes the GitHub Actions CI setup for running a custom code linter. It makes sure Docker can read and write build caches correctly and that the built linter image is available for later steps. There is no user-facing security fix here; it is purely a build-infrastructure improvement.

Lower-priorityMerge pull request #11498 from lightningnetwork/yy-claudell-ci-hold-labelby litbot-9000 · a86da23f · Nov 5, 2026 · 4 filesMessage 73 · AdequateTriage 0Details
Commit message · litbot-9000

Merge pull request #11498 from lightningnetwork/yy-claudell-ci-hold-label

ci: hold CI on new PRs until the ci-hold label is removed

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Lower-priorityMerge pull request #11489 from lightningnetwork/yy-claudell-ci-merge-tiersby litbot-9000 · 6fe0785e · Nov 5, 2026 · 3 filesMessage 73 · AdequateTriage 0Details
Commit message · litbot-9000

Merge pull request #11489 from lightningnetwork/yy-claudell-ci-merge-tiers

ci: split CI into pr, merge queue and nightly tiers

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Lower-prioritybuild: cache custom linter build in CIby Olaoluwa Osuntokun · aec7299d · Nov 5, 2026 · 3 filesMessage 80 · StrongTriage 0Details
Commit message · Olaoluwa Osuntokun

build: cache custom linter build in CI

In this commit, we make the tools Docker image build reuse a remote build
cache so the custom golangci-lint binary is no longer recompiled from
source on every lint run.

The lint job previously spent several minutes compiling the linter binary
on every cold runner, only for the next run to throw it away. We now set
up BuildKit with the GitHub Actions cache backend in the lint job, and
pass the cache configuration through a new DOCKER_BUILD_ARGS make
variable that is only populated when CI is set, so local builds keep
their existing behavior.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-priorityMerge pull request #11499 from lightningnetwork/yy-claudell-ci-gotmpdirby Olaoluwa Osuntokun · 465ec199 · Nov 5, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Olaoluwa Osuntokun

Merge pull request #11499 from lightningnetwork/yy-claudell-ci-gotmpdir

github: move Go's temporary build dir off /tmp

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discountmerge-commit duplicate discount
Lower-prioritydocs: add release note for #11501by litbot-9000 · 11aaece6 · Nov 5, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · litbot-9000

docs: add release note for #11501

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityci: skip matrix jobs at the job level outside their tierby litbot-9000 · 0682b115 · Nov 5, 2026 · 1 fileMessage 100 · StrongTriage 0Details
Commit message · litbot-9000

ci: skip matrix jobs at the job level outside their tier

The required matrix legs of unit-test, basic-integration-test,
cross-compile and dep-pin were kept instantiated in the pr and held
tiers and only skipped their steps, because a job-level condition is
evaluated before the matrix expands and a skipped matrix job never
reports the per-leg check names that the ruleset required. Every PR
push therefore occupied 13 runners for legs that did nothing, and a
held run 19.

Once CI result is the only required status check, those legs can be
skipped at the job level. The unit-test matrix is split into unit-test
(unit-cover and unit-module, all tiers) and unit-test-merge (the rest,
merge and nightly tiers) under the same name, so the check names stay
the same. basic-integration-test only runs in the merge and nightly
tiers, and cross-compile, unit-test and dep-pin skip at the job level
for documentation-only changes, drafts (cross-compile only) and held
runs.

CI result now lists unit-test-merge in its needs and tier lists, and
requires static-checks and lint in the pr tier. On pull requests it
lets the documentation-only and draft skips pass explicitly instead of
relying on step-level no-ops, and it requires check-commits on every
pull request run, so that the Check commits status check can be
dropped from the ruleset as well.

This must only merge after the ruleset requires CI result alone,
otherwise PRs wait forever for per-leg checks that are no longer
reported.

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
documentation-only discount