build(deps): bump github.com/lightningnetwork/lnd from 0.21.1-beta to 0.21.2-beta.rc1

[dependabot]

Bumps github.com/lightningnetwork/lnd from 0.21.1-beta to 0.21.2-beta.rc1.

Release notes

Sourced from github.com/lightningnetwork/lnd's releases.

lnd v0.21.2-beta.rc1

Database Migrations

This release introduces no new database migrations, but includes two important fixes to existing migration paths:

• The KV-to-SQL payment migration now handles historical routes containing an orphaned blinded total amount, preventing affected nodes from failing during startup.

• The channeldb migration recovery now detects databases missing the persisted version key and safely runs the previously skipped v0.21 waiting-proof migration.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.21.2-beta.rc1.sig and manifest-v0.21.2-beta.rc1.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.21.2-beta.rc1.sig manifest-v0.21.2-beta.rc1.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg:                using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

Verifying the Release Timestamp

From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.21.2-beta.rc1.txt.asc.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:

ots verify manifest-roasbeef-v0.21.2-beta.rc1.sig.ots -f manifest-roasbeef-v0.21.2-beta.rc1.sig

Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Verifying the Release Binaries

Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved. The release binaries are compiled with go1.26.3, which is required by verifiers to arrive at the same ones.

... (truncated)

Commits

• 54a2b5a Merge pull request #11043 from ziggie1984/bump-v0.21.2
• 75ab74b build: bump version to v0.21.2-beta.rc1
• 88ea937 Merge pull request #11039 from lightningnetwork/backport-11028-to-v0.21.x-branch
• 0c0e970 docs: add interceptor auto-fail height release note
• b021eb0 htlcswitch: bound intercepted auto-fail height
• 77f060e Merge pull request #11034 from lightningnetwork/backport-11032-to-v0.21.x-branch
• 0cdbe35 docs: update 0.21.2 release notes
• 20313a3 contractcourt: retain deadline across contest resolution
• 9be6159 Merge pull request #11020 from lightningnetwork/backport-10900-to-v0.21.x-branch
• 37ed474 Merge pull request #11031 from lightningnetwork/backport-11019-to-v0.21.x-branch
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)