getAlby / lndhub.go

Accounting wrapper for the Lightning Network. It provides separate accounts for end-users. (LndHub compatible API written in Go)
GNU General Public License v3.0
86 stars 23 forks source link

Bump github.com/lightningnetwork/lnd from 0.15.5-beta.rc2 to 0.16.0-beta.rc2 #334

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/lightningnetwork/lnd from 0.15.5-beta.rc2 to 0.16.0-beta.rc2.

Release notes

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

lnd v0.16.0-beta.rc1

Database Migrations

There are 4 migrations in the Watchtower client database that free up disk space by improving the storage layout and prepare for future optimizations around the watchtower functionality.

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.16.0-beta.rc1.sig and manifest-v0.16.0-beta.rc1.txt are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: Signature made Fri Feb 24 15:32:04 2023 PST
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.16.0-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.16.0-beta.rc1.sig.ots -f manifest-roasbeef-v0.16.0-beta.rc1.sig

Alternatively, the open timestamps 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.19.2, which is required by verifiers to arrive at the same ones. They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. Note that these are already included in the release script, so they do not need to be provided.

The make release command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then make release sys=<OS-ARCH> tag=<tag> can be used.

... (truncated)

Commits
  • d26cfd2 Merge pull request #7485 from Roasbeef/v0-16-0-branch-rc2
  • 8f4fc29 build: bump version to v0.16.0-rc2
  • 4b88020 Merge pull request #7446 from yyforyongyu/fix-future-msg
  • 54a1661 Merge pull request #7451 from CRex15/walletkit+labeltransaction
  • 5330b3e Merge pull request #7475 from lightningnetwork/dependabot/go_modules/tor/gola...
  • 2e9ceb2 Merge pull request #7471 from hieblmi/peer-alias-remove-error
  • 534535f build(deps): bump golang.org/x/net in /tor
  • c4e0927 Merge pull request #7453 from lightningnetwork/dependabot/go_modules/healthch...
  • 880dfd7 Merge pull request #7455 from lightningnetwork/dependabot/go_modules/tor/gola...
  • 910e383 docs: update release notes
  • Additional commits viewable in compare view


Dependabot compatibility score

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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@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)
dependabot[bot] commented 1 year ago

Superseded by #335.