v0.6.0 #1608
Roasbeef
announced in
Announcements
v0.6.0
#1608
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Database Migrations
tapd
v0.6.0
contains non-revertible database migrations. After runningtapd
v0.6.0
, these database migrations prevent downgradingtapd
to a previous release. Create backups oftapd
database state, before upgrading totapd
v0.6.0
. Please report any database migration issues.Breaking changes
See previous version
v0.5.1
release notes for changes prior tov0.5.x
.There are no breaking changes between
v0.5.1
andv0.6.0
, but grouped asset channel funding will only work with the next version of Lightning Terminal (v0.15.0-alpha
) which is going to be published soon.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-roasbeef-v0.6.0.sig
andmanifest-v0.6.0.txt
are in the current directory) with:You should see the following if the verification was successful:
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 Timestamp
In addition to time-stamping the git tag with OpenTimestamps, we also timestamp the manifest file along with its signature. Two files are included in our release artifacts:
manifest-roasbeef-v0.6.0.sig.ots
andmanifest-v0.6.0.txt.ots
.Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
Alternatively, the OpenTimestamps website can be used to verify these timestamps if one doesn't have a
bitcoind
instance accessible locally.Assuming you are using the OpenTimestamps
ots-git-gpg-wrapper
you can verify the timestamp of the git tag by verifying the tag as explained in Verifying the Release Binaries.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.23.9
, which is required by verifiers to arrive at the same ones.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, thenmake release sys=<OS-ARCH> tag=<tag>
can be used.Finally, you can also verify the tag itself with the following command:
Verifying the Docker Images
To verify the
tapd
andtapcli
binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):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
andtapd-source-v0.6.0.tar.gz
are in the current directory, follow these steps:The
-mod=vendor
flag tells thego build
command that it doesn't need to fetch the dependencies, and instead, they're all enclosed in the local vendor directory.Additionally, it's now possible to use the enclosed
release.sh
script to bundle a release for a specific system like so:⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
Release Notes (auto generated)
What's Changed
ContextGuard.Goroutine
by @ffranr in Proof of Concept: Simplifying Concurrency withContextGuard.Goroutine
#1380sync
loadtest by @GeorgeTsagk in Addsync
loadtest #1352SendPayment
&AddInvoice
by @GeorgeTsagk in Support group keys onSendPayment
&AddInvoice
#1423Proof.Bytes
by @ffranr in Add methodProof.Bytes
#1474PaymentBandwidth
uses HtlcView by @GeorgeTsagk inPaymentBandwidth
uses HtlcView #1462taprpc.AddInvoice
by @GeorgeTsagk in Allow setting sats/msats totaprpc.AddInvoice
#1448PublishTransaction
by @gijswijs in multi: Add label toPublishTransaction
#1411AddInvoice
multiple hop hints) by @GeorgeTsagk in Multi rfq receive (AddInvoice
multiple hop hints) #1457OutboundParcel.Copy
and add genericCopy
fn test by @bhandras in tapfreighter: fixOutboundParcel.Copy
and add genericCopy
fn test #1580New Contributors
Full Changelog: v0.5.1...v0.6.0
This discussion was created from the release v0.6.0.
Beta Was this translation helpful? Give feedback.
All reactions