chore: bump lnd to v0.20.1-beta

[im-adithya]

Bumps github.com/lightningnetwork/lnd from 0.20.0-beta.rc4 to 0.20.1-beta (Latest release)

Summary by CodeRabbit

• Chores
  • Updated dependency versions to resolve compatibility requirements and incorporate latest releases.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates go.mod by promoting two transitive dependencies (github.com/google/uuid and google.golang.org/protobuf) to direct dependencies, and bumping versions for github.com/lightningnetwork/lnd and github.com/lightningnetwork/lnd/sqldb.

Changes

Dependency Management

Layer / File(s)	Summary
Direct Dependency Promotion go.mod	github.com/google/uuid v1.6.0 and google.golang.org/protobuf v1.36.10 moved from indirect to direct require blocks.
Version Updates go.mod	github.com/lightningnetwork/lnd bumped from v0.20.0-beta.rc4 to v0.20.1-beta (direct); github.com/lightningnetwork/lnd/sqldb bumped from v1.0.11 to v1.0.12-0.20260113193010-8565d12e40b1 (indirect).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested reviewers

• rolznz

Poem

🐰 Dependencies hop and bound,
Direct paths now we have found,
Versions leap to futures bright,
Go.mod hops with pure delight!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: bumping the lnd dependency to v0.20.1-beta, which aligns with the primary modification shown in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-lnd-v0.20.1-beta

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@go.mod`:
- Line 267: The protobuf-go replacement version is out of sync with the lnd
bump: update the replacement that pins the protobuf module (the entry currently
ending with v1.30.0-hex-display) to v1.33.0-hex-display so it matches the
github.com/lightningnetwork/lnd v0.20.1-beta requirement; locate the go.mod
replacement for the protobuf module (the line referencing the hex-display
variant) and change its version suffix to v1.33.0-hex-display.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 298d739c-9ef2-4131-9326-0b05f82f9ad0

📥 Commits

Reviewing files that changed from the base of the PR and between fef6fc0 and 9722678.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (1)

• go.mod

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

For github.com/lightningnetwork/lnd v0.20.1-beta, what version/range of google.golang.org/protobuf is required in its go.mod, and are there known incompatibilities with protobuf-go forks pinned around v1.30.0?

💡 Result:

For github.com/lightningnetwork/lnd v0.20.1-beta, the required google.golang.org/protobuf version is pinned via go.mod to v1.33.0-hex-display (via a replace to a LightningLabs fork), rather than a google.golang.org/protobuf upstream semver range. Regarding incompatibilities with protobuf-go forks pinned around v1.30.0: I did not find any authoritative, source-backed report describing specific incompatibilities between lnd v0.20.1-beta and protobuf-go forks pinned to ~v1.30.0. The available evidence I found indicates lnd uses a forked/proxied google.golang.org/protobuf dependency (v1.33.0-hex-display), but it does not document (or I could not locate) known incompatibility details versus v1.30.0-pinned forks.

Citations:

• 1: https://github.com/lightningnetwork/lnd/blob/master/go.mod
• 2: https://github.com/lightningnetwork/lnd/tree/v0.20.1-beta.rc1/go.mod

---

🏁 Script executed:

# Check the go.mod file around line 277 to confirm the protobuf replacement
sed -n '270,280p' go.mod

Repository: getAlby/hub

Length of output: 461

---

Update protobuf-go-hex-display version to match lnd v0.20.1-beta requirement.

The protobuf replacement is currently pinned to v1.30.0-hex-display, but lnd v0.20.1-beta requires v1.33.0-hex-display. Update line 277 to pin v1.33.0-hex-display to ensure compatibility with the bumped lnd version and align with its declared dependencies.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@go.mod` at line 267, The protobuf-go replacement version is out of sync with
the lnd bump: update the replacement that pins the protobuf module (the entry
currently ending with v1.30.0-hex-display) to v1.33.0-hex-display so it matches
the github.com/lightningnetwork/lnd v0.20.1-beta requirement; locate the go.mod
replacement for the protobuf module (the line referencing the hex-display
variant) and change its version suffix to v1.33.0-hex-display.