Weekly Edition for Thursday, Jul 8
This is a general bug fix and maintenance release.
The full list of changes since 0.7.2-beta can be found here:
Verifying the Release
This marks the first minor release of the 0.13.x cycle. This release is primarily a maintenance release including several bug fixes that didn't make it into 0.13.0, a series of fixes for introduced regressions, and a few small optimizations.
Verifying the Release
In order to verify the release, you'll need to have
Once you have the required PGP keys, you can verify the release (assuming
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
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:
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
Alternatively, the open timestamps website can be used to verify timestamps if one doesn't have a
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
Finally, you can also verify the tag itself with the following command:
Verifying the Docker Images
To verify the
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
Additionally, it's now possible to use the enclosed
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️