quorum
quorum copied to clipboard
Bump github.com/btcsuite/btcd from 0.20.1-beta to 0.23.1
Bumps github.com/btcsuite/btcd from 0.20.1-beta to 0.23.1.
Release notes
Sourced from github.com/btcsuite/btcd's releases.
btcd v0.22.0-beta
This release of
btcd
is primarily to act as a catchup for the various changes that have accumulated.Verifying the Release
In order to verify the release, you'll need to have
gpg
orgpg2
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:Once you have the required PGP keys, you can verify the release (assuming
manifest-v0.22.0-beta.txt
andmanifest-v0.22.0-beta.txt.sig
are in the current directory) with:gpg --verify manifest-v0.22.0-beta.txt.sig
You should see the following if the verification was successful:
gpg: assuming signed data in 'manifest-v0.22.0-beta.txt' gpg: Signature made Tue 08 Jun 2021 10:07:53 AM EDT gpg: using DSA key 0DB39EAF526568682088EEDFB15210D35378BD54 gpg: Good signature from "John C. Vernaleo <[email protected]>" [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 withshasum -a 256 <filename>
, compare it with the corresponding one in the manifest file, and ensure they match exactly.Verifying the Release Binaries
As of this release, our release binaries are fully reproducible thanks to
go1.13
! Third parties are now 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 withgo1.16.5
, which is required by verifiers to arrive at the same ones.Finally, you can also verify the tag itself with the following command:
git verify-tag v0.22.0-beta
You should see something along the lines of this in the case of a valid tag:
gpg: Signature made Tue 08 Jun 2021 09:42:52 AM EDT gpg: using DSA key 0DB39EAF526568682088EEDFB15210D35378BD54 gpg: Good signature from "John C. Vernaleo <[email protected]>" [ultimate]
Building the Contained Release
Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming that
vendor.tar.gz
andbtcd-source-v0.22.0-beta.tar.gz
are in the current directory, follow these steps:tar -xvzf vendor.tar.gz tar -xvzf btcd-source-v0.22.0.tar.gz GO111MODULE=on go install -v -mod=vendor GO111MODULE=on go install -v -mod=vendor ./cmd/btcctl </tr></table>
... (truncated)
Commits
04aac1e
Merge pull request #1863 from Roasbeef/version-bump-23-1e6f6ba4
build: bump version to v0.23.18fc2d70
Merge pull request #1862 from bhandras/rpccliet-fix21696c63
Merge pull request #1844 from chappjc/getnewaddress-rpcclient-revertb2af777
rpcclient: fix missing returnb5fb9b0
Merge pull request #1860 from Roasbeef/version-bump-232ce3069
build: bump version to v0.23.0fd7f41c
Merge pull request #1840 from ellemouton/exportCheckStandardnessFunccee92e0
Merge pull request #1856 from bhandras/rpcclient-fix97313ac
rpcclient: save the last error when retrying- 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 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)